Capacity planning with example

-
Capacity planning is the process of determining the available resources, such as time and manpower, needed to successfully complete a project or sprint. It involves estimating the amount of work the team can handle within a given timeframe.

For a 5-person Scrum team working on a 2-week sprint, capacity planning involves calculating how much work each team member can realistically handle during that time period. This typically includes factoring in any potential constraints, such as holidays, meetings, or other responsibilities.

As an example, let's consider a 5-person Scrum team working on a project to improve the user interface of Gmail. Each team member has an average capacity of 6 hours per day for the sprint, taking into account any non-project related tasks.

Based on this capacity, the team estimates that they can allocate 30 hours per day (5 people x 6 hours) towards the project. Over a 2-week sprint, this amounts to 300 hours (30 hours/day x 5 days x 2 weeks).

By breaking down the project into tasks and estimating how long each task will take, the team can then determine if they have enough capacity to complete the project within the sprint timeframe. If the estimated work exceeds the team's capacity, adjustments may need to be made, such as re-prioritizing tasks or adding additional resources.

By effectively planning and managing the team's capacity, the Scrum team can ensure they are able to deliver a high-quality product within the desired timeframe.

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