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 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