Scrum- Anit Patterns
0 likes87 views
Scrum is an agile framework that uses short iterations and frequent delivery to develop products. Some common anti-patterns that can hurt Scrum productivity include absent stakeholders at sprint planning, outdated product backlogs, teams taking on more work than they can handle, and lack of preparation or participation at important Scrum events like daily stand-ups, sprint reviews, and retrospectives. Monitoring anti-patterns through tools like sprint burndown charts and discussions at retrospective meetings can help teams improve by addressing issues and making changes.
Scrum- Anit Patterns
- 1. A B C D Presented By: Arpit Gupta Scrum Anti Patterns
- 2. Lack of etiquette and manners is a huge turn off. KnolX Etiquettes Punctuality Join the session 5 minutes prior to the session start time. We start on time and conclude on time! Feedback Make sure to submit a constructive feedback for all sessions as it is very helpful for the presenter. Silent Mode Keep your mobile devices in silent mode, feel free to move out of session in case you need to attend an urgent call. Avoid Disturbance Avoid unwanted chit chat during the session.
- 3. Our Agenda 01 Introductions & Overview 02 Scrum Anti Patterns 03 Q&A
- 4. Overview Scrum is the most popular agile framework that encourages teams to work together. Much like how a rugby or football team trains for the big game, Scrum encourages the team to learn through experience, organize by tackling problems, reflect on wins and losses, and continually improve. Scrum uses an iterative and incremental development model with short iteration times. Scrum is relatively easy to implement and focuses on fast and frequent delivery ● Scrum team : A Scrum team is a collection of people (usually 5-9 members) who work together to deliver a desired increment of the product ● Product owner : The Product Owner in the Scrum team is responsible for the outcome of the project. The Product Owner seeks to maximize the value of the Product by managing and optimizing the Product Backlog. ● Scrum Master: A Scrum Master is an expert who uses Agile project management to guide a team through the course of a project. The Scrum Master facilitates all communication and collaboration between leadership and team players to ensure results.
- 5. ● Product backlog: A product backlog is a list of new features, changes to existing features, bug fixes, infrastructure changes, or other activities that a team can deliver to achieve a specific result. The Product Backlog is the single source of truth on which team will be working on. ● Sprint planning :The purpose of sprint planning is to define what the sprint can deliver and how that work will be accomplished. Sprint planning is done in collaboration with the entire Scrum team ● Daily Scrum: The purpose of the Daily Scrum is to review progress towards the sprint goals and adjust the sprint backlog by adjusting future planning work as needed. ● Sprint review meeting: The Sprint Review is an informal meeting at the end of the Sprint where the Scrum Team demonstrates what has been achieved during the period. ● Sprint retrospective: :A Sprint Retrospective is a regular meeting at the end of a Sprint to discuss what went well in the previous Sprint cycle and what could be improved in the next Sprint. Agile Sprint Retrospective is an integral part of the Scrum framework for developing, executing, and managing complex projects..
- 7. Anti-patterns are general different from bad practices because they are common practices that seem like reasonable solutions at first but ultimately result in bad consequences that outweigh the benefits. What is AntiPatterns?
- 8. Anti Patterns at Sprint Planning Meetings ● Absent Key Stakeholders ○ Product owners unable to resolve queries for a user story ○ Team members who need to take on tasks are absent and unable to check their availability ○ Developers unable to devote time to troubleshooting or ad-hoc work ● Having a Weak Definition of Done ○ The definition of done helps the team estimate the effort that must be expended to complete the task. If the DOD is weak, there can be confusion about what exactly counts as done. This delivers more than it needs and most of the time it doesn't do what you want it to do. Estimating how much effort each member put in is also very tedious in this scenario.
- 9. Outdated Product Backlog The Product Backlog contains items that haven't been touched in 6-8 weeks or longer. Either the PO doesn't have time to work on the Product Backlog or has delegated responsibility to a Scrum Master or development team. Outdated story in the product backlog Missing acceptance criteria The product backlog has user stories with no acceptance criteria. This happens when not enough time is spent reconciling the backlog or the requirements are too vague/complicated.
- 10. Dominant PO Product Owners create user stories by providing not just the "why", but the "how" and "what". This usually happens when the product owner has a technical background.
- 11. Anti Patterns at Daily Scrum ● Noise from Outside ○ Teammates talk about each other and interrupt. ○ A member of the team is not concentrating while others are giving presentations. ○ Team members do not join the daily standup on time and they join the stand up frequently late ● Discussing work in details ○ No time check ● Current Problems ○ Team members are unable to solve the problems they encounter and are unable to do their job. Other team members also do not offer assistance in such cases due to lack of time, trust or competence. ● Skipping Daily Scrum ● Not preparing for the meeting ○ Team members not able to speak about updates
- 12. Capacity Issues Development teams overestimate their capabilities and take on too many tasks. They don't think about setting aside time for planned vacation days, holidays, or mandatory sprint ceremonies. Team is working beyond capacity
- 13. Anti Patterns at Sprint Review ● Lack of Attendance ○ Stakeholders will be presented with less insight and feel that not enough information is being shared. ○ Stakeholders do not participate in the Sprint Review. (Stakeholders have several reasons for not participating in the Sprint Review: either they see no value in the event or they compete with another important meeting. They don't understand the importance of the Sprint Review meeting.) ● Unfinished business ○ A false sense of accomplishment can result if the developer does not complete the item as stated in the definition of done. This leads to a backlog and a bad reputation with stakeholders. ● Lack of preparation ○ Team members rushing the presentation can prevent stakeholders from understanding the purpose of a particular feature, which can be the result of a lack of preparation. It can also affect the effectiveness of the meeting and prevent stakeholders from attending the next one. ● Flow Impact ○ The Scrum Master allows stakeholders to interrupt the flow of the Scrum Team during the Sprint. A stakeholder can be anyone, such as a product owner, a developer's line manager, or even a senior member of management.
- 14. Variable Sprint length The Scrum Team extends the length of the sprint by a few days to reach the sprint goal. Attendees are bored with PowerPoint during sprint review. Development teams often develop PowerPoint presentations rather than demos of the actual increment itself. Death by PowerPoint
- 15. Anti Patterns at Sprint Retrospective ● Making Personal Attacks ● Skipping or Rushing Retro ● No actions taken
- 16. No Retro Session Either the team believes there is nothing to improve, or the development team has decided to spend time on future development work to meet the sprint goal and never look back.
- 17. CLEANING SERVICES How do you perceive Scrum anti-patterns?
- 18. Sprint burndown charts and retrospective meetings are the best detection mechanisms for Scrum anti-patterns. The Sprint Burndown Chart visualizes your team's work. This is a graphical representation of how quickly work is completed and how much work remains over time. A burndown chart is in no way a tool for punishing or rewarding development teams. Rather, they are used by the development team to focus on the goals of the sprint. Equally good at providing additional insight into all kinds of impediments, both at the team and organizational level.
- 19. Following key anti-patterns can be detected by just looking at the Sprint burn-down charts: ● Poorly managed external dependencies or complex (too large) stories selected during sprint planning ● Delayed approval by the Product Owner ● Increase in sprint goal scope in the middle of the sprint ● The team reaches the sprint goal much earlier than expected ● If the graph is above the expected progress line for the entire sprint, it indicates that the development team is making slow progress.
- 20. It is recommended to use the Sprint Burndown Chart pattern for your next retrospective meeting because it makes it easier to identify team issues and system malfunctions. The team can then discuss the identified issues and suggest improvement actions.
- 21. A Scrum anti-pattern is team member behavior that robs the Scrum team of resources in the long run. Monitoring such behavior in Scrum teams improves developer productivity and performance. These behaviors are sensitive and it is the responsibility of each member to report such instances to higher authority and reach out to those who can help them. Boost team morale and have a positive impact on team productivity. Conclusion
- 22. Thank You ! Get in touch with us: Lorem Studio, Lord Building D4456, LA, USA