Difference between revisions of "Piepsysteem/oppakken piepjes/en"
Jump to navigation
Jump to search
(Created page with "Category:Guidelines Category:Customers {{Parent}} ==Aanleiding== Tijdens het werken aan de sprints komen onvoorziene zaken naar voren. Daarop piepen wij en we parkeren di...") |
|||
| (12 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Guidelines]] [[Category:Customers]] | [[Category:Guidelines]] [[Category:Customers]] | ||
{{Parent}} | {{Parent}} | ||
| − | == | + | [[Category:Method]] |
| − | + | [[Category:Guidelines]] | |
| + | {{Languages|Piepsysteem/oppakken piepjes}} | ||
| + | == Motive == | ||
| + | While working on the sprints, unforeseen issues might come up. We then alert and we park those activities in a possibly todo container called 'sprint X' (in principle to be solved in a new sprint after the last offered sprint will be completed). | ||
| − | + | It is possible that the expectation arose that 2Value partners and associates still take extra cases with them in the same sprint. Often we do that (small "do this, do that" thing) but with the things we "squeak" on, that is not possible. | |
| − | == | + | == Steps to pick up 'to do's' that we alerted about == |
| − | + | What is the procedure for picking up items that we have indicated to be classified as 'sprint X' and / or moved to the 'sprint X' or 'Out of scope' working folder in the work management system? | |
| − | :1. | + | : 1. The customer decides how to proceed with a case that has been alerted: sprint X, have it executed immediately, have it performed differently, or halt the case; see the [[Alertsystem]] or the offer that the customer has received. |
| − | :2. 2Value ( | + | : 2. 2Value (and partners / associates) look at whether they can agree to proceed that way. Is capacity available (in terms of time and right expertise) in the current sprint? |
| − | :3. | + | : 3. Then we have to do the math: should there be an extra provision? |
| − | ===== | + | ===== Example 'sprint X' ===== |
| − | + | An example is: support on location of the internal ICT department for bringing the acceptance server into the air. | |
| − | + | There the steps were successively: 1. extra work requested, 2. yes it was possible, and 3. yes a budget was agreed that the associated firm can invoice. | |
| − | == | + | == Automatic way of picking up alerts == |
| − | <big> | + | <big> How will the process evolve when there is no intervention as in the above mentioned [[#Steps to pick up 'to do's' that we alerted about|steps]] </ big> |
| − | + | We most probably have lots to do in the current sprint of our projects. Hopefully in an enjoyable way. Alert-cases that a customer reports, can only be taken into consideration after the completion of the current sprint / phase. | |
| − | {{Ambox|type=delete|text=''' | + | {{Ambox | type = delete | text = '' 'To enhance clarity about sprint X' '': <br/> <br/> In case of an alert case in 'sprintX' nothing can be done without further decisionS, and will not be delivered in the next and / or last sprint, but only added to the queue of planned work after payment has been agreed or received}}} |
Latest revision as of 13:02, 20 February 2019
Parent: Piepsysteem/oppakken piepjes
| Language: | Nederlands • English |
|---|
Contents
Motive
While working on the sprints, unforeseen issues might come up. We then alert and we park those activities in a possibly todo container called 'sprint X' (in principle to be solved in a new sprint after the last offered sprint will be completed).
It is possible that the expectation arose that 2Value partners and associates still take extra cases with them in the same sprint. Often we do that (small "do this, do that" thing) but with the things we "squeak" on, that is not possible.
Steps to pick up 'to do's' that we alerted about
What is the procedure for picking up items that we have indicated to be classified as 'sprint X' and / or moved to the 'sprint X' or 'Out of scope' working folder in the work management system?
- 1. The customer decides how to proceed with a case that has been alerted: sprint X, have it executed immediately, have it performed differently, or halt the case; see the Alertsystem or the offer that the customer has received.
- 2. 2Value (and partners / associates) look at whether they can agree to proceed that way. Is capacity available (in terms of time and right expertise) in the current sprint?
- 3. Then we have to do the math: should there be an extra provision?
Example 'sprint X'
An example is: support on location of the internal ICT department for bringing the acceptance server into the air.
There the steps were successively: 1. extra work requested, 2. yes it was possible, and 3. yes a budget was agreed that the associated firm can invoice.
Automatic way of picking up alerts
How will the process evolve when there is no intervention as in the above mentioned steps </ big>
We most probably have lots to do in the current sprint of our projects. Hopefully in an enjoyable way. Alert-cases that a customer reports, can only be taken into consideration after the completion of the current sprint / phase.
 |
'To enhance clarity about sprint X' : In case of an alert case in 'sprintX' nothing can be done without further decisionS, and will not be delivered in the next and / or last sprint, but only added to the queue of planned work after payment has been agreed or received |
}
