Difference between revisions of "Release planning/en"

From 2value wiki 2
Jump to navigation Jump to search
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Languages|Release planning}}
 
[[Category:Methodiek]]
 
[[Category:Methodiek]]
−
[[Category:Richtlijn]]
+
[[Category:Richtlijnen]]
 
{{Image|name=Release256px|width=256px|pad=20px|ilink=File:Release256px.png|float=right}}
 
{{Image|name=Release256px|width=256px|pad=20px|ilink=File:Release256px.png|float=right}}
  
−
'''For Associates: use the associate access level of the [[Associate:Release planning|Release planning page]] for examples.'''
+
'''For Associates: use the associate access level of the [[private:Associate:Release planning|Release planning page]] for examples.'''
  
 
=The what, why and how of release planning=
 
=The what, why and how of release planning=
 
==What is it?==
 
==What is it?==
−
<big>Release planning is per project a derivative of the offer and the calls (and status of these)</big>
+
<big>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.</big>
  
 
==Why should there be a release plan in place?==
 
==Why should there be a release plan in place?==
Line 29: Line 30:
 
##2Value searches for the optimum mix of deliverables, the right path to be able to deliver them and the priorities they have been given.   
 
##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''',  
 
  Please note: priorities of the customers are not leading: '''the 2Value method is''',  
−
  established in commissioning the project (refer to [[CM|Contract management]])
+
  established when the project was initiated (refer to [[CM|Contract management]])
  
 
=== Resource planning===
 
=== Resource planning===
Line 36: Line 37:
  
 
==2Value release planning with [[SLA]] Medium and Pro ==
 
==2Value release planning with [[SLA]] Medium and Pro ==
−
#The attachment of the SLA contract is leading, after that the SLA contract. The 2Value method determines the pace of the planning. The customer can assign priorities.  
+
#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:
 
#calls are submitted by:
 
##SLA manager for periodical maintenance  
 
##SLA manager for periodical maintenance  
−
##Associates that want to take a precautionary measurement or want that this is taken.
+
##Involved associates that want to take a precautionary measurement or indicate that these need to be taken.
 
##the customer
 
##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.  
 
: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.  
Line 45: Line 46:
  
 
==2Value release planning with SLA basic (former individual strip card) ==
 
==2Value release planning with SLA basic (former individual strip card) ==
−
#De strippenkaart is een los - vaste werkrelatie tussen klant en 1 of meer associates die op de strippenkaart zijn ingedeeld
+
#The strip card is a flexible working relationship between customer and 1 or more associates that have been assigned to the strip card. 
−
#Soms geeft de klant aan met welke associate hij zou willen werken. Dat kan. Maar beschikbaarheid en experts bepaalt wie 2Value kan aanbieden.
+
#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.  
−
#De associate geeft zijn redelijke planning van implementatie van functionaliteiten (de "release")
+
#The associate indicates a reasonable implementation planning of the functionality (the "release")
−
#Over de voorwaarden van de losse strippenkaart en de belangrijke rol die 2Value speelt zie
+
#Please refer to ##[[Strip Card]]##[http://www.2value.nl/nl/diensten/support SLA Basic (losse) strippenkaart aanbod] for more information about the conditions of the individual strip card and the important role 2Value has in it.
−
##[[Strippenkaart]]
+
#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.
−
##[http://www.2value.nl/nl/diensten/support SLA Basic (losse) strippenkaart aanbod]
+
#calls are submitted by:
−
#De bijlage van het Strippenkaart contract is leidend, daarna het Strippenkaart contract zelf. Vervolgens bepaalt de betreffende associate het tempo in de planning. De klant kan prioriteiten toekennen.
+
##the customer
−
#calls worden ingeschoten door:
+
##Associate(s) that want to take a precautionary measurement
−
##de klant
+
##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.  
−
##Betreffende associate(s) die een preventieve maatregel wil(len) nemen
 
−
## Betreffende associate(s) die uren die overblijven van een strippenkaart (einde looptijd) gebruiken om kennis, documentatie en staat van het systeem te verversen.
 
 
<includeonly>
 
<includeonly>
−
{{Ambox|type:content|text=Let wel: prioriteiten klant zijn niet leidend: de associate planning van best effort gegeven zijn agenda des te meer.<br/>
+
{{Ambox|type:content|text=Please note: priorities of a customer are not leading: the Associate planning of best effort in relation to his/her diary is.<br/>
−
#Capaciteitsplanning is een zaak van De klant kan
+
#Capacity planning is a matter of the customer. He can:
−
##extra associates op het strippenkaart contract plaatsen. Let wel dit verhoogt de onderlinge afstemming en verhoogt daarmee het deel overhead in ''afgestempelde'' uren.
+
##add extra associates to the strip card contract. This does increase the amount of time spent on mutual alignment and the overhead when it comes to  ''stamped'' hours.
−
##zwaar wegende klachten neer leggen bij [[CEO]]. Geen operationele zaken.
+
##address the [[CEO]] with his (severe) concerns. No operational issues.
 
}}
 
}}
 
</includeonly>
 
</includeonly>
  
−
==Overige gerelateerde zaken==
+
==Other related issues==
−
#Het halen van een deadline en daarbij het ''kritieke pad'' e.d.: [[Zwakste_schakel]]
+
#Meeting the deadline and maintaining the ''right path'' etc.: [[Zwakste_schakel]]
−
#2Value bepaalt ''na overleg met klant'' '''altijd zelf''' de inhoud en [[PM|volgorde van ontwikkeling]] in een project. Vooral bij krappe deadlines.
+
#2Value determines ''after consultation with the customer'' '''always''' the content and [[PM|order of developments]] in a project herself. Particularly if the deadline is tight.
−
#Intern: [[Associate:Role:contractmanagement#2Value_wil_contractueel_haar_methodiek_overeen_komen |contractmanagement drijfveren]]
+
#Internally: [[Associate:Role:contractmanagement#2Value_wil_contractueel_haar_methodiek_overeen_komen |contract management mainsprings]]
−
#prioritering wordt bij intake / orientatie overleg bepaald. [[Testing/Bevindingen evalueren|Bevindingen en Prioriteiten]] worden geëvalueerd.
+
#Priorities are determined during intake / orientation. [[Testing/Bevindingen evalueren|Findings and Priorities]] are evaluated.
  
−
==Bottomline==
+
==Bottom line==
−
  Aan een vastgestelde release (projectfase met milestone) wordt ''niets'' toegevoegd
+
  ''Nothing'' is added to a set release (project phase with milestone).
  
−
===Te rigide?===
+
===Too rigid?===
−
Voor flexibiliteit hebben we de [[SLA/basic|strippenkaart]].
+
For flexibility we have the [[SLA/basic|strip card]].
−
<sup>Daarop werken we dan tussentijdse verzoeken af. Garantie ''best effort'' en binnen beschikbare ''timeslots''</sup>
+
<sup>Interim requests are deducted from this strip card. Guarantee is ''best effort'' and within available ''time slots''</sup>

Latest revision as of 13:25, 9 December 2013

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?

  1. To enable 2Value style project management
  2. To meet holy deadlines in whichever way possible
  3. To manage the expectations of the customer


Release planning of projects and SLA

2Value release planning with projects

  1. The offer is leading, the 2Value method sets the tempo in planning and the customer can assign priorities.
  2. 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

    1. Customer indicates delivery dates
    2. 2Value builds in buffers
    3. 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

  1. 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).
  2. Capacity planning is part of resource planning.

2Value release planning with SLA Medium and Pro

  1. 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.
  2. calls are submitted by:
    1. SLA manager for periodical maintenance
    2. Involved associates that want to take a precautionary measurement or indicate that these need to be taken.
    3. 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.
  1. 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)

  1. The strip card is a flexible working relationship between customer and 1 or more associates that have been assigned to the strip card.
  2. 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.
  3. The associate indicates a reasonable implementation planning of the functionality (the "release")
  4. 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.
  5. 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.
  6. calls are submitted by:
    1. the customer
    2. Associate(s) that want to take a precautionary measurement
    3. 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.


Other related issues

  1. Meeting the deadline and maintaining the right path etc.: Zwakste_schakel
  2. 2Value determines after consultation with the customer always the content and order of developments in a project herself. Particularly if the deadline is tight.
  3. Internally: contract management mainsprings
  4. 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

Retrieved from "http://wiki.2value.nl/index.php?title=Release_planning/en&oldid=14044"