Tag-arkiv: agile

User Stories – del og hersk

Forleden havde jeg en snak med en (ScrumMaster) kollega …. sådan lidt løst og fast om at skrive stories. På et tidspunkt kom vi til at tale om at splitte user stories. Jeg er stor fortaler for at user stories maks er 1-2 team-arbejsdage. Min erfaring er at dette giver stories som er lette for teamet at over/gennemskue og at de derfor kan komme med et godt og retvisende estimat.

Tegn på at du skal splitte din story:

  • Teamet udtrykker stor risici i form at ny teknologi eller eksterne afhængigheder.
  • Der er mange acceptkreterier. Man afgører selv hvad mange er, men mit bud er mere end 10.
  • Det tager dig mere en 5 minutter at forklare teamet essensen af story’en.
  • Teamet estimere mere end 5 story-points.

Stories vekselkurs

Når man splitter en story sker der ofte det at det samlede estimat stiger. Det virker måske umiddelbart som en dum ide at splitte når nu det kommer til at “koste” mere!

story_exchange_rate

 

Et højt estimat er udtryk for en usikkerhed. Så et estimat på 13 betyder ikke bare 13 story points bum! Det betyder 8-20 story points. De fleste går efter at få så retvisende planer som muligt, så derfor giver splitning god mening. Og det kan godt være at det på papiret ser ud som en dårlig forretning for PO’en men det han opnår er sikkerhed. Sikkerhed for at estimatet holder. Sikkerhed for at han får det han ønsker og som giver forretningsværdi. Og hvem vil ikke gerne have det.

Så man veksler et lille estimat med stor usikkerhed til et større estimat med lille usikkerhed.

Så mit råd til dig som Product Owner er at sørge for at du laver små overskuelige stores, for både teamets og din egen skyld. Det ekstraarbejdet er givet godt ud.

God splitning!

Beer-Background

Tillid er ikke noget man først skal fortjene

Hvis du har et team der ikke performer så giv dem din fulde tillid. Det kan være med til at hjælpe dem til at komme op af “sumpen” og komme i omdrejninger igen.

I denne uge jeg haft fornøjelsen at være lave en gæsteforelæser hos Thomas TøthCBS. Publikum var 3.-semesters projektlederstuderende. Det var en spændende oplevelse og der var mange gode spørgsmål fra salen.

CBS – Et spørgsmål om tillid v06 (9 MB)

Den gode product owner, en nøgle til agil success

Sammen med min kollega Christine Berkmann afhold jeg den 2. Juni 2014 et gå-hjem møde hos BestBrains.

Med udgangspunkt i vores hverdag i SafeCom talte vi om hvordan man som Product Owner har indflydelse på hvor godt (eller dårligt) ens team performer.

Der er speaker notes på slides’ene så man kan få noget ud af det uden at have været der.

Præsentation: PO Cafemøde 2014-06-02 (4 MB)

PO Cafemøde 2014-06-02 v02

PDP – Pregnancy Driven Planning

This post was originally posted November 8th 2012 on “The Voice” (internet for Nuance Communication)

Notice: This post has nothing to do with family planning!

I’m in the lucky circumstances that my wife is pregnant expecting our second child. She was actually supposed to deliver last Friday. This means that I’m sort of in a limbo-state at work, ready for take-off in case the water breaks. It has been that for the last couple of weeks.

Here in Denmark the father gets a two-week leave right after the birth. This means that I have to be ready to take two weeks “vacation” … just like that.

In the beginning I felt it a bit annoyed not knowing if I would show up at work tomorrow or not. But I tried to turn it into something positive. Actually it was not something I did on purpose I can just see now that this is how it ended up.

Not knowing if I will be at work tomorrow (and the next two weeks) have helped me focus on some things:.

  • I try to do the most value-adding tasks first.
  • I try to device my tasks into smaller pieces – that can be completed within a couple of hours.
  • I’ve gotten better at documenting the current state of my work.
  • I’m more focused at keeping others up-to-date with what I do.
  • I more or less have someone standby to fill in for me.
  • Why postpone things that you can do it today?

I think that improves my work effectiveness if I always had a pregnant wife a home on the edge to going into labor. However I don’t think that my wife thinks that is a good idea 😉

I think that we all should try to work like “we might not be here the next two weeks”. For me it triggered a more agile way of working (on a personal level).

If we try to apply this to a team I think that it is good that you are able to cover for each other. And here I’m not talking about covering up but about helping each other out. In a team it is also important that you have a good feeling about where you colleges are and what they are doing. As a team member you can help this by putting into words what you are doing and discussing it with your peers.

I have not developed the model to its full potential, but so far I call it Pregnancy Driven Planning or just PDP (because we are in IT).

See you tomorrow …. Perhaps!?!

–Rasmus