Gausmohiyuddin Maniyar

11 Scrum Artifacts: A Beginner's Guide [2024] - Simplilearn 11 Scrum Artifacts: A Beginner's Guide [2024]  Simplilearn

6

𝗗𝗼𝗻'𝘁 𝗠𝗮𝗸𝗲 𝗠𝘆 𝗠𝗶𝘀𝘁𝗮𝗸𝗲 🚨! Over the past few years, I've accumulated 50+ professional certifications: • PMI-PfMP, PMI-PMP, PMI-ACP, PMI Micro-Credentials in Agile Metrics and Value Stream Mapping • Scrum PSPO 2, PSM2, PSU, PSK, PAL, PSD • IIBA-ECBA, IIBA-CPOA • SAFe-POPM • AIPMM - CPM • ICP - ACC • Intuit D4D • Prince2 Practitioner • Oracle SQL Certified Associate • IEEE Certified Software Engineering Master • Microsoft (x5 certs), AWS (x2 certs) Impressive list, right? 𝗗𝗶𝗱 𝘁𝗵𝗲𝘆 𝗵𝗲𝗹𝗽 𝗺𝗲 𝗹𝗮𝗻𝗱 𝗺𝘆 𝗱𝗿𝗲𝗮𝗺 𝗷𝗼𝗯? Surprisingly, a big fat NO. 𝗗𝗶𝗱 𝗜 𝗲𝘅𝗽𝗮𝗻𝗱 𝗺𝘆 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻 𝗻𝗲𝘄 𝗰𝗼𝗻𝗰𝗲𝗽𝘁𝘀? Absolutely, YES. 𝗪𝗮𝘀 𝗶𝘁 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝗶𝗻𝘃𝗲𝘀𝘁𝗺𝗲𝗻𝘁 𝗼𝗳 𝗺𝘆 𝘁𝗶𝗺𝗲 𝗮𝗻𝗱 𝗺𝗼𝗻𝗲𝘆? On reflection, probably not. Some people even assume that I know nothing about product management just because I stacked multiple project management certificates hahaha! Let's dive into the 𝗽𝗿𝗼𝘀 𝗮𝗻𝗱 𝗰𝗼𝗻𝘀 of my certification journey: Pros: 🔝𝗦𝗸𝗶𝗹𝗹 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗺𝗲𝗻𝘁: Each certification brought a new set of skills and knowledge. I felt more competent in each subject area. 🔝𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴: The training sessions were fantastic for meeting like-minded professionals and expanding my network. Some people I met in intensive workshops brought me tons of advisory and consulting opportunities. 🔝𝗖𝗿𝗲𝗱𝗶𝗯𝗶𝗹𝗶𝘁𝘆: Certifications can (in rare cases) add weight to your resume, showing potential employers your dedication and commitment to the field. Cons: 👎🏻𝗡𝗼 𝗚𝘂𝗮𝗿𝗮𝗻𝘁𝗲𝗲𝗱 𝗝𝗼𝗯𝘀: Certifications alone don't promise a job. It's the experience, soft skills, and how you apply what you learn that matters. 👎🏻𝗧𝗶𝗺𝗲-𝗖𝗼𝗻𝘀𝘂𝗺𝗶𝗻𝗴: Some of these certifications took months of preparation to sit for the exam. Time that could have been invested elsewhere. 👎🏻𝗘𝘅𝗽𝗲𝗻𝘀𝗶𝘃𝗲: The costs add up. Not just for the exam but for the materials, classes, and sometimes even travel. Why did I do them? I was, and still am, obsessed with being a well-rounded PM during the first 10 years of my career. So professional certifications were one of the possible ways that gave me the chance to discover areas like project management, business analysis, AI, and more. In conclusion, while I don’t regret the path I've taken (every experience is a lesson after all), I would advise young professionals to strike a balance. Don't just chase certifications; chase experiences, real-world projects, and continuous learning. That, combined with a few strategic certifications, can be a real game-changer in your career. Would love to hear your thoughts on this. Have certifications played a pivotal role in your career? 🤔 #technology #startups #ProductManagement #ProductManager #product

45

11 Comments

🚀 Mastering Scrum in Software Development 🚀 Scrum has become an essential methodology for building successful software products efficiently and with high adaptability! If you're in tech, you’ve likely encountered this framework, but here’s why it stands out and some fundamentals for making it work for you and your team. 🛠️ What is Scrum? Scrum is an Agile framework that enables software development teams to work in structured “sprints” (typically 2-4 weeks) to deliver parts of a project incrementally. Instead of a long, rigid plan, Scrum allows for iterative development, adapting to changing requirements and continuous feedback. 👥 Roles in Scrum Product Owner: Manages the product backlog, sets priorities, and ensures the team delivers maximum value. Scrum Master: Facilitates the Scrum process, removes blockers, and ensures the team follows Agile principles. Development Team: Cross-functional members who do the actual work to deliver a “potentially shippable product increment” by the end of each sprint. 🔄 Key Artifacts Product Backlog: The prioritized list of work items (features, bugs, tech debt) for the product. Sprint Backlog: A subset of the Product Backlog chosen to be completed in a specific sprint. Increment: The working product version that grows with each sprint and is tested, reviewed, and ready to go live. 📅 The Scrum Ceremonies Sprint Planning: Set sprint goals and decide on backlog items to complete. Daily Standups: 15-minute sync meetings to align and tackle blockers. Sprint Review: Team demos their work to stakeholders, receiving feedback. Sprint Retrospective: Reflect on the past sprint to improve team efficiency. 🎯 Benefits of Scrum Flexibility: Adjusts priorities and requirements based on client feedback. Transparency: Frequent interactions and feedback foster visibility for both teams and stakeholders. Continuous Improvement: Retrospectives allow teams to learn from each sprint. Faster Delivery: Smaller, more manageable deliverables keep projects moving forward efficiently. 📝 Getting Started with Scrum Commit to Scrum values: Respect, courage, focus, openness, and commitment. Use the right tools: Software like JIRA, Trello, or Azure DevOps can streamline your process. Regular communication: Foster a culture of open and constructive feedback. 🔗 Free Scrum Resources to Master Agile Scrum.org: scrum.org/ Agile Alliance: agilealliance.org/ Atlassian's Scrum Guide: atlassian.com/agile/scrum/ Scrum transforms how teams tackle projects, making it indispensable in software development. Give it a try if you haven’t already! 👍 𝗟𝗶𝗸𝗲 if you found it helpful! 🔁 𝗥𝗲𝗽𝗼𝘀𝘁 with your network! #Scrum #Agile #SoftwareDevelopment #Productivity #TechCommunity #TechLife #ProjectManagement #ScrumMaster #ProductOwner #SoftwareEngineering #TeamCollaboration #DailyStandup #ProjectPlanning #AgileMethodologies #TechLeadership #Development

5

AGILE FAD 😉 REDUCTION (https://lnkd.in/eJFikjp4) is one of the cornerstones of the "HEXAGON of focus" for KSTS Consulting Agile FAD 😏  Reduction increases chances of a "SAFe Recovery" 😆 (https://lnkd.in/enFmGDNu)  –and is a conscious organizational effort, geared towards a gradual reduction of misunderstanding, misinterpretation, errors and omissions, associated with a widespread “let’s do agile” industry trend. The need for these reduction efforts has become more urgent over the last couple of years, as many organizations have gone down the wrong path of fast-tracking their agile transformations, in broad and shallow ways, without making any meaningful, systemic improvements. Many such agile FADs have been manifested through “big bang” installations of large, commercially available frameworks, accompanied by tooling solutions, and usually promoted by large consultancies, with ladder being financially rewarded by frameworks and tooling companies. If you recognize any of the below “FADs” (the list is not conclusive and only most commonly seen FADs is listed), you may wish to consider doing a very comprehensive look-back reassessment (a.k.a. enterprise-wide retrospective) of what your organization has done, how much it cost and, very importantly, what was the achieved #roi. Organizational & Transformational Leadership: -Mid-level management, #pmo, centralized “power towers”, leading agile transformation -Too many town hall motivational speeches, with little action -Senior managers, delegating learning to subordinates and not doing GEMBA -Senior managers, not staying around long enough to see/take responsibility for their decisions -Large consulting agencies, providing guidance at astronomically high costs   Budgeting/Finance: -Budgets, remaining fixed and fiscal-year-end based (as opposed to becoming flexible/dynamic) -Budgets, traditionally cascading down from portfolios, to programs and projects -Budgets, not being defined for properly defined products -Funding temporary, short-lived project teams -Funding single-function specialty/component teams   #hr Norms & Policies: -Continuing individual performance appraisals (IPA) -Coupling individual performance with bonuses and other financial perks -Having too many organizational/reporting layers and command & control management style -Not being able to provide a competitive compensation that attracts top talent workers -Having big gaps between compensation of managers and workers   Products: -Falling into a trap of “everything is a product” (fake productization) -Creating convoluted structures of products / “sub”- and “sub-sub”-products -Defining products around technology domains, not business/customer use areas -Defining products, based on a traditional reporting structure -Not involving key business stakeholders in a product definition...   Read more at: https://lnkd.in/eJFikjp4

8

4 Comments

Brief of Scrum: Journey Scrum is an Agile framework for managing complex projects, particularly in software development. It emphasizes iterative progress, collaboration, and adaptability. Here’s a brief overview: 1. Core Roles:   - Product Owner: Defines and prioritizes product requirements, focusing on maximizing value.   - Scrum Master: Facilitates Scrum practices, removes obstacles, and ensures the team stays focused.   - Development Team: Cross-functional group responsible for delivering increments of the product. 2. Key Events (Ceremonies):   - Sprint: A fixed time-box (usually 1-4 weeks) where the team works on a set of tasks.   - Sprint Planning: Team defines sprint goals and selects backlog items to work on.   - Daily Stand-Up (Daily Scrum): A short, daily meeting to discuss progress and address blockers.   - Sprint Review: Team presents completed work to stakeholders for feedback.   - Sprint Retrospective: Team reflects on the sprint to identify improvements for the next cycle. 3. Artifacts:   - Product Backlog: An ordered list of tasks or features, prioritized by the Product Owner.   - Sprint Backlog: A subset of the product backlog selected for the sprint.   - Increment: The working product outcome at the end of each sprint. Scrum focuses on delivering working software frequently, adapting plans based on feedback, and continuously improving through regular reflection. It’s popular for its structure yet flexibility, allowing teams to tackle complex projects effectively. Courtesy: Mahesh Mallikarjunaiah

18

1 Comment

#projectmanagement #opinionpiece #agileprojectmanagement Project Life Cycles (aka approaches or development life cycles) can be Predictive (plan-driven/waterfall), Adaptive (agile), Iterative, Incremental, or a hybrid. A NOTEWORTHY RESOURCE Agile Glossary and Terminology | Agile Alliance https://lnkd.in/e2HdWfX3

1

1 Comment

how you can master the common problem solving techniques used by Agile coaches ? Mastering common problem-solving techniques used by Agile coaches involves a combination of understanding Agile principles, practicing specific techniques, and developing soft skills. 1. Understand Agile Principles Agile Manifesto: Familiarize yourself with the four values and twelve principles of the Agile Manifesto. Agile Frameworks: Gain a solid understanding of Scrum, Kanban, Lean, and other Agile methodologies. 2. Learn and Practice Problem-Solving Techniques A. Root Cause Analysis (RCA) 5 Whys: Keep asking "why" until you reach the root cause of a problem. Fishbone Diagram (Ishikawa): Visually map out the potential causes of problems. B. Brainstorming Encourage open and free-flowing ideas from team members without judgment. Use techniques like Mind Mapping to visually organize ideas. C. Retrospectives Conduct regular retrospective meetings to reflect on what went well, what didn’t, and what can be improved. Use frameworks like Start-Stop-Continue, 4Ls (Liked, Learned, Lacked, Longed For), or Sailboat (anchors, wind, rocks, and land). D. SWOT Analysis Analyze Strengths, Weaknesses, Opportunities, and Threats related to a project or a team. E. Value Stream Mapping Visualize the flow of materials and information to understand and optimize the process. 3. Develop Soft Skills Facilitation: Learn to guide meetings effectively, ensuring every voice is heard and the team stays on track. Conflict Resolution: Develop techniques to manage and resolve conflicts within the team. Communication: Enhance your ability to communicate clearly and listen actively. Coaching: Learn coaching techniques to empower team members and encourage continuous improvement. 4. Get Hands-On Experience Join an Agile Team: Participate in an Agile team as a member or coach to gain practical experience. Simulations and Workshops: Attend or organize role-playing simulations and workshops to practice problem-solving in a controlled environment. 5. Use Tools and Software Familiarize yourself with Agile tools like Jira, Trello, and Miro, which can help in visualizing and managing Agile practices and problem-solving techniques. 6. Solicit Feedback and Reflect Regular Feedback: Seek feedback from peers, mentors, and team members about your problem-solving approach. Self-Reflection: Regularly reflect on your experiences and identify areas for improvement. theoretical knowledge with practical experience and continuous learning, you can master the common problem-solving techniques used by Agile coaches and effectively support Agile teams. #agile #agilecoach #safe #scrum

7

Nice way to visualize the scrum framework - an agile approach to develop and release software products. #scrum #sprintplanning #backlog #userstory #productowner #retrospective

16

Check out this video of Talia McCune's workshop, "Poster Pro: Create engaging flipchart posters to wow in workshops " from #AgileIndia 2023. #AgileMindset #HandDrawnVisuals #Workshop #AgileCoaching #DiversityinTech

1