agilemantis - the approved Scrum Add On for MantisBT

Transcription

1 agilemantis - the approved Scrum Add On for MantisBT Working with capacities Version: Date: Ranking: Field: Filename: public agilemantis short_documentation.agilemantis.5.capacity.en gadiv GmbH Bövingen Much Telefon Telefax info@gadiv.de

2 Table of contents 1 Why working with capacities in agilemantis? Capacity Management Manage Availability Manage Standard Availability Manage Calendarian Availability Manage Developer Capacity Enter performed work in a Task Further Reading... 8 > > short_documentation.agilemantis.5.capacity.en 2 / 8

3 1 Why working with capacities in agilemantis? You are properly planning your Sprints using well confirmed velocities from the past. However that planning again and again leads to incomplete Sprints. The clear reason: When team members are on leave, in hospital, in advanced education, then velocities for a complete Team don t match the reality. Obviously realistic Sprint velocity must be taken member by member with respect to their true capacity. That is the moment to take into use the capacity utilities of agilemantis. With this, erroneous planning is well prevented. > > short_documentation.agilemantis.5.capacity.en 3 / 8

4 2 Capacity Management Work can be entered in many ways: Every User Story can be estimated with Story Points. Under "Manage availability" you can set when and how long each developer is available for a period of time. Under "Manage developer capacity" you can set when and how long each developer is available for a given Sprint. In each Task you enter the remaining work and gradually reduce this value by entering your performed work. These values (if given) will be used by agilemantis During the Sprint Planning in order to warn if there the capacity is lower than the planned work (automatically). in a running Sprint in order to warn if there is not enough capacity (automatically) / generate Burndown information (Statistics) in closed Sprints in order to generate and show Velocity and other charts. 2.1 Manage Availability Availability for the company is deposited : As typical Standard for all weekdays. As true values for each day in the Calender. The standard is put in just once for the longer future. E.g. "Peter is in house each Thursday for 4 hours, Mary is in house each workday for 8 hours". The true calendar is typically put in at the beginning of each Sprint. To save time, the standard capacity can be taken for this and only the few deviations must be edited then Manage Standard Availability Login: agilemantis administrator 1. Main menu: agilemantis Manage Availability 2. Shows "Manage Standard Availability", 3. For each member insert a value for each weekday > > short_documentation.agilemantis.5.capacity.en 4 / 8

5 4. Press Save Manage Calendarian Availability 1. Press Open calendar at "Manage Standard Availability". 2. Press Save Standard which will adopt the standard values. 3. If necessary, adjust your values. 4. Press Save all. This directs you back to the Standard Availability. 5. Choose the next developer. > > short_documentation.agilemantis.5.capacity.en 5 / 8

6 2.2 Manage Developer Capacity During the Sprint Planning is the best opportunity to enter developer capacities. In the Sprint Backlog / Taskboard click Manage Developer Capacity. Here you can enter the capacity for each developer of the team in the chosen Sprint. The view with a calendar opens for each member of the team. You can enter a value (in hours) for each day of the Sprint. 1. Main Menu: Sprint Backlog [Backlog] opens the Sprint Backlog 2. At "Edit Sprint Backlog" press Manage Developer Capacity. 3. If appropriate: Press Complete with Availability. This replaces all zero capacity values by the Standard Availability values. 4. Enter the values for each member and day of the Sprint. 5. Press Save. This directs you back to the Sprint Backlog. > > short_documentation.agilemantis.5.capacity.en 6 / 8

7 2.3 Enter performed work in a Task In the Expert Components you can enter the performed work as shown below: A double click on the free area opens the Task dialogue. In the lower half of this dialogue you can find the fields Planned Work, Remaining Work and Performed Work. The Planned Work is either set at the beginning of the sprint or when creating the task. You will find a similar function in the open source part of agilemantis. In the field "Performed Work" you can gradually enter the actual performed work. Every value will be added to the total performed work and reduces the planned work of a Task. > > short_documentation.agilemantis.5.capacity.en 7 / 8

8 3 Further Reading This document is part of the following series of introductive tutorials: The Open Source Package: Installation and system requirements The Open Source Package: Init The Open Source Package: Performing the first Sprint The Expert Components. Working with Capacities. > > short_documentation.agilemantis.5.capacity.en 8 / 8