What exactly a zero planning means?

-

Zero planning, also sometimes called "zero sprint," is the preparation part of a project cycle. In your interview, try to explain what zero planning is and why it exists in the Scrum framework to demonstrate that you understand its important function. To provide a thorough answer, consider describing your personal experience with zero planning and how you successfully prepare for projects.

Example: “Zero planning happens at the start of a project to ensure the team meets all of the requirements listed. As a Scrum master, I have a basic outline for my zero planning sprints.

First, I review the requirements with the client and my product manager. We want to make sure we understand exactly what the client wants from the product or service. Then, I gather all of my resources, including the right team members and material needs. After that, I plan the sprints. I like to make sure my team can complete the sprint within that amount of time by outlining the basics for each week, sometimes each day.

I try to utilize my zero planning time to create a smooth project plan with a successful end result. I believe zero planning has enabled me to be an effective Scrum master.”


Sprint 0 COVERAGE : 

1. Team structure - Team Onboarding, Roles n responsibilities of both client and partners. 

2. Backlog management - Story creation, Acceptance Criteria, Story sizing and Story Splitting. 

3. Training’s - Functional, Technical and Agile. 

4. Process - 

Collaboration tool configuration ie. Jira / TFS/Rally, Communication Tools - WebEx / Video Conference setups among team members. 

Agile Delivery approach - Sprint cadence, Metrics, Governance, Quality Practices. 

Test Strategy and Deployment Strategy. 

5. Environment - Development Environment Readiness, Testing Environment Readiness. 

Access - Application access to the team.

Comments

Post a Comment

Popular posts from this blog

What is the ‘Navigating the Scrum Events’ Series?

-
Image
Source: https://www.scrum.org/resources/blog/navigating-scrum-events-sprint-review What is the ‘Navigating the Scrum Events’ Series? If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each Scrum Event. If your team is more experienced but you feel like you’re drifting away from healthy behaviors and patterns and you’re not sure how to course correct - you can use this series as a baseline to reset and start re-aligning your team. This is NOT the end-all-be-all perfect way to operate for all scenarios - but a straight-to-the-point tactical list of steps to help you get to the basic outcomes you need at the end of the event. The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Sprint Review - What’s The Point? The purpose of the Sprint Review straight from   the Scrum Guide  is “to inspect the outcome of the Sprint and determine future adaptations”. The key to this instance of “in...
Read more

CAPACITY PLANNING IN AGILE SCRUM

-
Image
  1.       What is Capacity Planning? 2.       Benefits of Capacity Planning 3.       How to do the Capacity Planning 4.       Examples of Capacity Planning 5.       Excel Template Sample What is Capacity Planning? CAPACITY PLANNING is the Available bandwidth or Productive hours of the Team members to deliver the product. PRODUCTIVE HOURS: The number of hours that the team members could spend to do the Actual work in the project Actual Hours: The Actual hours will be calculated after deducting the hours planned for the sprint events / ceremonies For Example: If the team members work 8 hours per day around 6 hours will be considered as Productive hours Remaining 2 hours will be used for sprint events , internal discussions Availability will be measured in Hours CAPACITY PLANNING will be done for the Team members for the Ent...
Read more

Burn down chart and burn up chart

-
Both Burn down chart and burn up chart are showing the progress of a team in a sprint. The burn up chart is just inverted version of burn down chart. 1.What is the point in having 2 charts? 2. In which scenarios burn down chart is useful? 3. In which scenarios burnup chart is useful? 4. In which scenarios you use only burn down and which scenarios you use only burn up? 1. What is the point in having 2 charts? Burn Down Chart : Tracks how much work remains to be completed over time. It gives a clear indication of whether the team is on track to finish the sprint or project on time. Burn Up Chart : Tracks the amount of work completed as well as the total scope of work, which includes any changes in the scope over time. Having both charts allows you to see: Burn Down : Focuses on how much work remains. Burn Up : Focuses on progress made and shows scope changes (i.e., if more work is added or removed from the sprint). This dual approach gives a fuller picture of progress, sc...
Read more