June 2011

10 Things to do in Sprint 0

 

Quite often Scrum projects and teams assume that they can start developing as from day 1 of the project.

This is only partially true and depends on your definition of ‘Start of the project’.

 

If ‘Start of the project’ for you is defined as “we have our team ready, give me the prioritized backlog, we’ll estimate so we can start developing”, then you can indeed start developing immediately.

However in most of the cases, you don’t have a backlog, a team... ready when the GO for a project is given. In these cases you need to do a ‘Sprint 0’.

Hoe Scrum de waterval binnensmokkelen

Werk je in een waterval en in sterk gereguleerde projecten? Gooi de Scrumgedachte niet overboord, maar smokkel ze zachtjesaan binnen. Met pragmatisme bereik je meer dan met fundamentalisme. Videoblog van Rini van Solingen.

 

Follow this | 23 jun 2011

 

The Curse of the Carddecks, Tax on your Product Backlog and Tango!

Your portion of certified value adding agile links ;-)

 

 

Fibonacci must die!

The curse of the carddecks

http://practicalagility.blogspot.com/2011/06/fibonacci-must-die.html

 

What's in a story?

How to break-up functionality into stories

http://blog.agilebuddy.com/2010/12/whats-in-a-story-breaking-things-down.html

 

Risk management - The Risk Rule of Three

 

Risk management is one of the more important aspects in project management.

As project manager your responsibility is to help your team to avoid and get rid of the issues and risks that lay all over the bumpy road towards project success.

On the other hand there is also a risk :-)  that you’ll spend much valuable time in analyzing and finding mitigations for things that might never occur.

 

So how should you tackle it then?

My (pragmatic and default) answer: use your common sense.

To avoid spending too much time on unsure, useless things but still be able to identify the most important risks for your project, I developed a simple guideline. I call it my Risk Rule of Three).

ScrumTips: 13 jun. - 17 jun.

 

Every day we release a new Scrum tip for all you agile folks out there. 
These tips are released last week, you could have received these tips much earlier: Follow us on Twitter 


Why Scrum? - An explanation, the satirical way

Not sure what Scrum is? A quite satirical movie of a developing team explaining why they implemented scrum.

 

Follow this | 17 jun. 2011

About agile deathmarches, agile learning plateaus, agile sins and getting paid more

Your portion of certified value adding agile links ;-)

 

 

Why you should pay the developers in Scrum more

Responsibilities in Scrum

http://www.scrum-breakfast.com/2010/08/responsibilities-in-scrum-or-scrum.html

 

The plateauing of an agile learning process

And what to do about it

http://www.netobjectives.com/blogs/reflections-on-sqe-conferences-west-2011

 

DoRR - Definition of Ready for Release

We are all familiar with the definition of ready and with the definition of done for stories on a scrum project. But as mentioned many times by many people the DoD of a story is often not enough to relase the 'Done' story to our customers.

That is why terms like DoD and concepts like 'Done, Done' were introduced. I would like to present you (yet) another one :-) : DoRR.

 

ScrumTips: 6 jun - 10 jun.

 

Every day we release a new Scrum tip for all you agile folks out there. 
These tips are released last week, you could have received these tips much earlier: Follow us on Twitter 


Scrum to manage your organization

We do agile: we do XP, (A)TDD, KanBan, a bit of Lean and ... Rugby!

Rugby, yes. Oh, it is called Scrum?!

 

Follow this | 09 june 2011

Seven tools to make you a better Product Owner, how Taylor strikes back in software and some other interesting stuff

Your portion of certified value adding agile links ;-)

 

 

Seven tools for the Product Owner

Alistair Cockburn picks the best from KANO, InnovGames and others

http://alistair.cockburn.us/7+tools+for+the+product+owner

 

Taylorism strikes back on software development

15 years after Kent Beck's XP

http://alistair.cockburn.us/Taylorism+strikes+software+development

 

Follow this | 7 june 2011

About the prisoner's dilemma for programmers, about Lean and sabres

Your portion of certified value adding agile links ;-)

 

 

Finding a product owner is not that hard

Finding a product owner with sifficient power is another thing

http://agilescout.com/enable-and-equip-your-product-owners/

 

Prisoner's dilemma in programming

Think carefully, very carefully

http://raganwald.posterous.com/the-programmers-dilemma-95099

 

ScrumTips: 30 may - 3 jun.

 

Every day we release a new Scrum tip for all you agile folks out there. 
These tips are released last week, you could have received these tips much earlier: Follow us on Twitter