Should a team be allowed to add more work to an ongoing Sprint?

-
Should a team be allowed to add more work to an ongoing Sprint?
The main goal of a Scrum team is to deliver value with each Sprint and this can not be achieved with half-done items. 
To deliver value in each Sprint a Scrum team needs to deliver potentially shippable increment(s) which meet the definition of done. Most of the times Developers are not able to finish all the work as planned and negotiate with the Product Owner to move back some work to the Product Backlog without affecting their Sprint goal. However, there are rare cases where a team feels that they are going to finish everything early or before time. Should a team be allowed to add more work to their ongoing Sprint in such cases?
Just as a team is allowed to drop work if things are not going as per plan they should be allowed to add work if they feel they are going to complete their planned work before time. The work committed to during Sprint planning is just a forecast by the Developers based on their past experience/velocity which cannot be perfect all the time.
As per Mike Cohn Teams are normally reluctant to bring in new work into a sprint because they are afraid that they will not be able to finish it within the Sprint. There is nothing wrong in having a partially done item at the end of a sprint. The problem is when a team is partially done with a lot of things or worse they are partially done with everything. Its better for a team to finish with five and a half product backlog items rather than stop after five and not start the sixth item.
Teams should avoid having multiple items unfinished, be sure to have at least something done every sprint. But don't stop your team from starting on an additional item near the end of a sprint even if they know they can't finish.
Finishing everything is always the goal, but sometimes bringing an extra item into a sprint and partially completing it has its own benefits.
A Scrum Master is not the traditional Project Manager; do you want to be a Scrum Master and feel that you have the required qualities to become a successful Scrum Master?
If yes, and interested message or mail me at ramanan.iyer@gmail.com for a free evaluation. I am a certified Scrum Master and Product Owner with 20+ years of experience in IT and have successfully trained students from India, USA, Canada, Australia, South Africa, Singapore, Denmark, Philippines and UAE in getting certified as Scrum Masters.
#scrummastercertification #scrum #scrummaster #scrumtraining #scrummastertraining #scrumcertification

Comments

Post a Comment

Popular posts from this blog

What Does a SM-SCRUM MASTER do “All the Day”

-
What Does a SM-SCRUM MASTER do “All the Day” ·         Facilitate the Daily Scrum (Timeboxed) o    Facilitate the Daily scrum meetings for the team and maintaining the time box ·         Arrange the Follow-up meetings o    Arrange the follow-up meetings for the detailed discussion after the daily scrum meeting, if anything is raised in the daily scrum meeting ·         Meeting with the PO – PRODUCT OWNER o    To arrange the meeting with the PO to support the Backlog creation and the Road Map preparation ·         Facilitating the SCRUM EVENTS   o    such as – BACKLOG REFINEMENT, SPRINT PLANNING, SPRINT REVIEW AND SPRINT RETROSPECTIVE meetings. ·         Meetings with the Team’s Manager                     o  SM will have the meetings with the Team’s manager to discuss about the people’s issues, Trainings etc. ·         Contribute to Community of Practice o    SM with communicate with the other SM’S and contribute to the Agile community of practice in the company
Read more

When to choose scrum and when to choose kanban? Explained with examples

-
Scrum and Kanban are two popular frameworks used in Agile project management. The choice between Scrum and Kanban depends on the nature of the project and the team's preferences. Here are some examples of when to choose Scrum and when to choose Kanban: When to choose Scrum: 1. Complex projects with evolving requirements: Scrum is suitable when the requirements of a project are likely to change during the development process. It allows for flexibility and iterative development with regular feedback loops. Example: Developing a new software product where the requirements are not fully known initially. The Scrum framework enables the team to adapt to changing customer needs and deliver a more satisfactory product. 2. Projects that require rigorous planning and structured timelines: Scrum is beneficial when a project requires a strict timeline and frequent checkpoints for progress assessment. The framework provides a clear structure for planning and organizing work. Example: Building a
Read more

Kanban board setup for AMS teams in SAP

-
To set up a Kanban system for AMS teams in SAP, you can follow these steps: 1. Define the workflow: Understand the specific stages involved in the AMS (Application Management Services) process. This can include stages like ticket creation, assignment, analysis, development, testing, deployment, and closure. Determine the sequence and dependencies of these stages. 2. Create Kanban columns: Map each stage of the AMS process to a separate column on the Kanban board. For example, create columns like "To Do," "In Progress," "In Review," "Ready for Deployment," and "Completed." 3. Define work item types: Classify the types of work that the team will handle. This can include different types of tickets or tasks like bug fixes, enhancements, or system configurations. Assign a specific color or label to each work item type. 4. Set WIP limits: Establish work-in-progress (WIP) limits for each column to avoid bottlenecks and promote smooth flow. Def
Read more