DEVELOPERS ORIENTEDPROJECT MANAGEMENT

robert @pankowecki

@arkency

WHY SUCH TALK?arkency.join(!arkency)

AGENDAsmall storiesunassigned taskstake the first onebig tickets - howto

1. STORY OF SIZE 14hrs (max2days)business valueindivisible

1 WEEK STORYalienationstressful

SMALL STORIES - BENEFITS #1easier to track progressclosure ritualcollective ownershipppl mobile acrossprojects

SMALL STORIES - BENEFITS #2Minimize risk of notdeliveringDeliver features graduallyPrioritize better

SMALL STORIES - EXAMPLE3 weeks of worksplit in 35 storiesEvery day something newdeployed

EXAMPLE

2. LEAVE TASKS UNASSIGNEDWhy?

WHY UNASSIGNED?ITERATION PLAN

REALITY

WHY UNASSIGNED?FreedomMangingriskElasticity

WHAT HAPPENS WHEN PM ASSIGNS TASKS?

WHAT HAPPENS WHEN DEVS ASSING TASKS?

WHERE IS YOUR COLLECTIVE OWNERSHIP?

IS IT IMMEDIATELY CLEAR TO YOU IN YOURCURRENT PROJECT WHAT YOU SHOULD BE

WORKING ON AS A DEVELOPER?

3. TAKE THE FIRST TASKfrom prioritizedbacklog

'TAKE IT' DOES NOT MEAN TO FINISH ITsurprisingly

IT'S OK TO ASSIGN SOME TASKSclear rulesgoodworkflow

4. HOW TO DEAL WITH BIG STORY?

UPFRONT

SPECIFICATION AS FLOATING TICKET

ASSUMPTION: TEAM WANT TO LEARN ANDIMPROVE

TLDR: 4 TECHNIQUESSmall storiesLeave them unassignedTake the first taskExtract small tasks fromspecification

BENEFITSCollective OwnershipMore asyncQuit the self-reinforcing loopDeliver business value andlearn

INTERESTED?

( ) available thanks to the courtesy of

http://blog.arkency.com/developers-oriented-project-management/Ebook cover image CCDavid DeHetre

25% DISCOUNTuse coupon 4DEVELOPERShttps://arkency.dpdcart.com/

THANK YOU 4DEVELOPERShttp://robert.pankowecki.pl/4developers/index.htmlhttp://blog.arkency.com/2013/09/story-of-size-1/http://blog.arkency.com/2013/10/refactor-to-remote-leave-tasks-unassigned/http://blog.arkency.com/2013/10/take-the-first-task/http://blog.arkency.com/2013/11/chronos-and-kairos/