Difference between revisions of "Piepsysteem/oppakken piepjes/en"

From 2value wiki 2
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
[[Category:Guidelines]] [[Category:Customers]]
 
[[Category:Guidelines]] [[Category:Customers]]
−
==Aanleiding==
+
{{Parent}}
−
Tijdens het werken aan de sprints komen onvoorziene zaken naar voren. Daarop piepen wij en we parkeren die activiteiten naar sprint X (in principe op te lossen in een nieuwe sprint na de laatst geoffreerde oplevering).
+
[[Category:Method]]
−
 
+
[[Category:Guidelines]]
−
Mogelijk ontstaat de verwachting is ontstaan dat 2Value partners en associates extra zaken ook meteen in dezelfde sprint nog meenemen. Vaak doen we dat wel (kleine "doe dit, doe dat" dingetjes) maar bij de zaken waarover we "piepen" kan dat dus niet.
+
{{Languages|Piepsysteem/oppakken piepjes}}
−
 
 
−
==Stappen oppakken piep==
 
−
Wat is de procedure voor het oppakken van zaken waarover we aan de bel hebben getrokken.
 
−
 
 
−
:1. De klant besluit over hoe verder te willen met case waar een piep op zit: sprint X, meteen laten uitvoeren, anders laten uitvoeren, of stoppen; zie de [[Piepsysteem]] of de aanbieding die de klant heeft ontvangen.
 
−
 
 
−
:2. 2Value (en partners/associates) bekijkt of we die route kunnen bewandelen. Is er capaciteit beschikbaar (in termen van tijd en juiste expertise) in de huidige sprint?
 
−
 
 
−
:3. Vervolgens maken we de urenbalans op: moet er een extra voorziening komen?
 
−
 
 
−
=====Voorbeeld=====
 
−
Een voorbeeld is: ondersteuning op locatie van de interne ICT afdeling voor het in de lucht brengen van de acceptatieserver.
 
−
 
 
−
Daar waren de stappen achtereenvolgens: 1. extra werk aangevraagd, 2. ja het kon, en 3. ja er is een budget afgesproken dat Lucius kan factureren.
 
−
 
 
−
==Automatische manier van oppakken pieps==
 
−
<big>Hoe gaat het zonder in te grijpen via de bovenstaande [[#Stappen oppakken piep|stappen]]?</big>
 
−
 
 
−
we gaan ervan uit dat we op een plezierige manier de handen vol hebben aan onze projecten.  Dus alle piep-cases die een klant ziet staan, nemen we pas mee na de oplevering van de sprint/fase.
 
−
 
 
−
{{Ambox|type=delete|text='''Voor de duidelijkheid over sprint X''':<br/><br/> De zaken die in de piep-cases staan worden worden zonder ander besluit volgens [[#Stappen oppakken piep|de bovenstaande route]] ook niet opgeleverd in de huidige, volgende en/of laatste sprint, maar pas daarna opgepakt.}}
 
−
 
 
−
 
 
−
 
 
−
[[Category:Guidelines]] [[Category:Customers]]
 
−
==Aanleiding==
 
−
Tijdens het werken aan de sprints komen onvoorziene zaken naar voren. Daarop piepen wij en we parkeren die activiteiten naar sprint X (in principe op te lossen in een nieuwe sprint na de laatst geoffreerde oplevering).
 
−
 
 
−
Mogelijk ontstaat de verwachting is ontstaan dat 2Value partners en associates extra zaken ook meteen in dezelfde sprint nog meenemen. Vaak doen we dat wel (kleine "doe dit, doe dat" dingetjes) maar bij de zaken waarover we "piepen" kan dat dus niet.
 
−
 
 
−
==Stappen oppakken piep==
 
−
Wat is de procedure voor het oppakken van zaken waarover we aan de bel hebben getrokken.
 
−
 
 
−
:1. De klant besluit over hoe verder te willen met case waar een piep op zit: sprint X, meteen laten uitvoeren, anders laten uitvoeren, of stoppen; zie de [[Piepsysteem]] of de aanbieding die de klant heeft ontvangen.
 
−
 
 
−
:2. 2Value (en partners/associates) bekijkt of we die route kunnen bewandelen. Is er capaciteit beschikbaar (in termen van tijd en juiste expertise) in de huidige sprint?
 
−
 
 
−
:3. Vervolgens maken we de urenbalans op: moet er een extra voorziening komen?
 
−
 
 
−
=====Voorbeeld=====
 
−
Een voorbeeld is: ondersteuning op locatie van de interne ICT afdeling voor het in de lucht brengen van de acceptatieserver.
 
−
 
 
−
Daar waren de stappen achtereenvolgens: 1. extra werk aangevraagd, 2. ja het kon, en 3. ja er is een budget afgesproken dat Lucius kan factureren.
 
−
 
 
−
==Automatische manier van oppakken pieps==
 
−
<big>Hoe gaat het zonder in te grijpen via de bovenstaande [[#Stappen oppakken piep|stappen]]?</big>
 
−
 
 
−
we gaan ervan uit dat we op een plezierige manier de handen vol hebben aan onze projecten.  Dus alle piep-cases die een klant ziet staan, nemen we pas mee na de oplevering van de sprint/fase.
 
−
 
 
−
{{Ambox|type=delete|text='''Voor de duidelijkheid over sprint X''':<br/><br/> De zaken die in de piep-cases staan worden worden zonder ander besluit volgens [[#Stappen oppakken piep|de bovenstaande route]] ook niet opgeleverd in de huidige, volgende en/of laatste sprint, maar pas daarna opgepakt.}}
 
−
 
 
−
2053/5000
 
−
[[Category: Guidelines]] [[Category: Customers]]
 
 
== Motive ==
 
== Motive ==
−
While working on the sprints, unforeseen issues come to the fore. We then squeak and we park those activities to sprint X (in principle to be solved in a new sprint after the last offered completion).
+
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.
 
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 pick up beep ==
+
== Steps to pick up 'to do's' that we alerted about ==
−
What is the procedure for picking up items that we have heard 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 a beep: sprint X, have it executed immediately, have it performed differently, or stop it; see the [[Pump System]] or the offer that the customer has received.
+
: 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) looks at whether we can walk that route. Is capacity available (in terms of time and right expertise) in the current sprint?
+
: 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 make the hour balance: should there be an extra provision?
+
: 3. Then we have to do the math: should there be an extra provision?
  
−
===== Example =====
+
===== Example 'sprint X' =====
 
An example is: support on location of the internal ICT department for bringing the acceptance server into the air.
 
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 Lucius can invoice.
+
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 pieps ==
+
== Automatic way of picking up alerts ==
−
<big> How does it go without intervening through the above [[Picking up steps [stepping] steps]] </ 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 assume that we are full of our projects in a pleasant way. So all the peep-cases that a customer sees standing up, we take with them only after the completion of the sprint / phase.
+
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 = '' 'For clarity about sprint X' '': <br/> <br/> The cases that are in the beep cases are being changed without any other decision according to [[#Stappen picking up the above route]] is not delivered in the current, next and / or last sprint, but only arrested afterwards}}}ß
+
{{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

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

}

Retrieved from "http://wiki.2value.nl/index.php?title=Piepsysteem/oppakken_piepjes/en&oldid=15648"