Release planning/en
Jump to navigation
Jump to search
Language: | Nederlands • English |
---|
For Associates: use the associate access level of the Release planning page for examples.
The what, why and how of release planning
What is it?
Release planning is a plan with a date of only the first delivery. A plan which lays out the overall project. The release plan is then used to create iteration plans for each individual iteration.
Why should there be a release plan in place?
- To enable 2Value style project management
- To meet holy deadlines in whichever way possible
- To manage the expectations of the customer
Release planning of projects and SLA
2Value release planning with projects
- The offer is leading, the 2Value method sets the tempo in planning and the customer can assign priorities.
- Calls are dealt with by the concerning associate and the customer. The customer can again prioritize these after the method has done this with the key issues.
Release planning
- Customer indicates delivery dates
- 2Value builds in buffers
- 2Value searches for the optimum mix of deliverables, the right path to be able to deliver them and the priorities they have been given.
Please note: priorities of the customers are not leading: the 2Value method is, established when the project was initiated (refer to Contract management)
Resource planning
- 2Value makes a detailed resource planning based on the release planning. 2Value starts work (response time) and can meet deadlines if ALL RESOURCE IS AVAILABLE (read: the packing list is delivered).
- Capacity planning is part of resource planning.
2Value release planning with SLA Medium and Pro
- The attachment of the SLA contract is leading, followed by the SLA contract. The 2Value method determines the pace of the planning. The customer can assign priorities.
- calls are submitted by:
- SLA manager for periodical maintenance
- Involved associates that want to take a precautionary measurement or indicate that these need to be taken.
- the customer
- the customer can again prioritize these after the 2Value SLA / 2Value method has done this with key issues. Please note: priorities of the customer are not leading: the 2Value method is as the customer has agreed to this.
- Capacity planning is part of the SLA process, with the SLA manager as responsible character.
2Value release planning with SLA basic (former individual strip card)
- The strip card is a flexible working relationship between customer and 1 or more associates that have been assigned to the strip card.
- In some cases the customer indicates with which associate he wishes to work. That's possible. But availability and experts determine who 2Value can offer.
- The associate indicates a reasonable implementation planning of the functionality (the "release")
- Please refer to ##Strip Card##SLA Basic (losse) strippenkaart aanbod for more information about the conditions of the individual strip card and the important role 2Value has in it.
- The attachment of the Strip Card contract is leading, followed by the Strip Card contract itself. The involved associate sets the tempo of the planning, the customer can assign priorities.
- calls are submitted by:
- the customer
- Associate(s) that want to take a precautionary measurement
- Involved associate(s) that want to use remaining hours on a strip card (that's about to expire) for knowledge, documentation and checking the state of the of the system.
- Meeting the deadline and maintaining the right path etc.: Zwakste_schakel
- 2Value determines after consultation with the customer always the content and order of developments in a project herself. Particularly if the deadline is tight.
- Internally: contract management mainsprings
- Priorities are determined during intake / orientation. Findings and Priorities are evaluated.
Bottom line
Nothing is added to a set release (project phase with milestone).
Too rigid?
For flexibility we have the strip card. Interim requests are deducted from this strip card. Guarantee is best effort and within available time slots