33
A Force of One Agile and the Solo Developer Clint Edmonson, Architect Evangelist, Microsoft

A Force of One - Agile and the Solo Developer

Embed Size (px)

DESCRIPTION

Ever been invited to a project kickoff party only to find out that you’re flying solo? Congratulations, you’ve just become the ultimate co-located, self-organized, cross-functional, energized agile team of one. Join us for this session where we explore how the lone coder can take advantage of the best agile has to offer in this era of ever shrinking budgets.

Citation preview

Page 1: A Force of One - Agile and the Solo Developer

A Force of OneAgile and the Solo Developer

Clint Edmonson, Architect Evangelist, Microsoft

Page 2: A Force of One - Agile and the Solo Developer

Why are we alone?

Page 3: A Force of One - Agile and the Solo Developer

What are we working on?

Page 4: A Force of One - Agile and the Solo Developer

What do we need?

Page 5: A Force of One - Agile and the Solo Developer

Do more with less!

Thanks Microsoft!

Page 6: A Force of One - Agile and the Solo Developer

Agenda

Agile PracticesWhat are the practices relevant to a solo developer?

Defining SuccessHow can we tell if we’re winning?

Opening MovesWhere should I start first?

Page 7: A Force of One - Agile and the Solo Developer

Agile Practices

Page 8: A Force of One - Agile and the Solo Developer

Intent Driven Development

Page 9: A Force of One - Agile and the Solo Developer

BusinessValue

Vision documentUser storiesSingle project backlogCustomer contact

Page 10: A Force of One - Agile and the Solo Developer

User StoriesBrowse Catalog Biz Value: 5

As a shopper I want to browse the Tailspin Toys catalog so that I may purchase some toys.

Estimate: 3

Front

Acceptance Criteria:

− Shopper is shown a list of product categories.

− Shopper can view details for each product in catalog, including :

name, inventory #, description, price, and related items.

Back

Page 11: A Force of One - Agile and the Solo Developer

Single Project Backlog

Page 12: A Force of One - Agile and the Solo Developer

Time ToMarket

ColocationRelative size estimatesSmall batch sizesContinuous integrationFrequent releasesResearch spikes

Page 13: A Force of One - Agile and the Solo Developer

Relative size estimates (RELATIVE SIZE IS!)

Page 14: A Force of One - Agile and the Solo Developer

Small batch sizes

Page 15: A Force of One - Agile and the Solo Developer

Quality ToMarket

Test driven requirementsTest driven development (Red-Green-Refactor)Done Done stateBugs before features

Page 16: A Force of One - Agile and the Solo Developer

Flexibility Emergent architectureSimple design (YAGNI)Aggressive refactoring (green code only)

Page 17: A Force of One - Agile and the Solo Developer

Simple design(YAGNI)

Page 18: A Force of One - Agile and the Solo Developer

Simple design(YAGNI)

Page 19: A Force of One - Agile and the Solo Developer

Visibility Single project backlogInformation radiatorsCustomer demos

Page 20: A Force of One - Agile and the Solo Developer

Personal Kanban boardBacklog Work In Progress Done!

Page 21: A Force of One - Agile and the Solo Developer

Personal Kanban board evolvedReady Work In Progress [3] Done!

Pen

Backlog

Page 22: A Force of One - Agile and the Solo Developer

Product Longevity

Coding standardsAutomated functional testsSustainable pace

Page 23: A Force of One - Agile and the Solo Developer

Sustainable pace

Page 24: A Force of One - Agile and the Solo Developer
Page 25: A Force of One - Agile and the Solo Developer

Success Factors

Collaboration with customerAttention to qualityIncrementalismAutomationContinuous improvementEnergized workforce

Page 26: A Force of One - Agile and the Solo Developer

Anti-patterns

No definitive processHuge casesTechnical debtLarge, complex, high-risk projects

Page 27: A Force of One - Agile and the Solo Developer
Page 28: A Force of One - Agile and the Solo Developer

Where do I start?

User storiesSingle project backlogRelative size estimationSmall batch sizesSimple design (YAGNI)Sustainable pace

Page 29: A Force of One - Agile and the Solo Developer

The role of tools

Page 30: A Force of One - Agile and the Solo Developer

TFS vNext Cloud Preview

Try it out for free

URL: https://tfspreview.com/ Passcode: UltimateTFSCloudPreview

Page 31: A Force of One - Agile and the Solo Developer

“Try everything. Go with what works.” Buckaroo Banzai

Page 32: A Force of One - Agile and the Solo Developer

ReferencesAgile Adoption Patterns - ElssamadisyAgile in a Flash – Langr and OttingerAgile Project Management with Scrum – SchwaberClean Code – MartinPersonal Kanban: Mapping Work | Navigating Life - BensonPractices of an Agile Programmer – Subramaniam & HuntThe Agile Sumurai – RasmussonSucceeding with Agile – CohnUser Stories Applied – Cohn

Page 33: A Force of One - Agile and the Solo Developer

Clint EdmonsonArchitect EvangelistMicrosoft

[email protected]@clintedwww.notsotrivial.net