Developers Oriented Project Management

robert @pankowecki

@arkency

Why such talk?

arkency.join(!arkency)

Agenda

• small stories
• unassigned tasks
• take the first one
• big tickets - how to

1. Story of size 1

• 4hrs (max 2days)
• business value
• indivisible

1 week story

• alienation
• stressful

Small stories - Benefits #1

• easier to track progress
• closure ritual
• collective ownership
• ppl mobile across projects

Small stories - Benefits #2

• Minimize risk of not delivering
• Deliver features gradually
• Prioritize better

Small stories - Example

• 3 weeks of work
• split in 35 stories
• Every day something new deployed

Example

2. Leave tasks unassigned

• Why?

Why unassigned?

Iteration Plan

Reality

Why unassigned?

• Freedom
• Manging risk
• Elasticity

What happens when PM assigns tasks?

What happens when Devs assing tasks?

Where is your Collective Ownership?

Is it immediately clear to you in your current project what you should be working on as a developer?

3. Take the first task

• from prioritized backlog

'Take it' does not mean to finish it

• surprisingly

It's ok to assign some tasks

• clear rules
• good workflow

4. How to deal with big story?

Upfront

Specification as floating ticket

Assumption: Team want to learn and improve

TLDR: 4 techniques

• Small stories
• Leave them unassigned
• Take the first task
• Extract small tasks from specification

Benefits

• Collective Ownership
• More async
• Quit the self-reinforcing loop
• Deliver business value and learn

Interested?

• http://blog.arkency.com/developers-oriented-project-management/
• Ebook cover image (CC) available thanks to the courtesy of David DeHetre

25% discount

• use coupon WROCLOVERB
• https://arkency.dpdcart.com/

Thank you #wrocloverb