a force of one - agile and the solo developer

Post on 09-May-2015

3.413 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

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.

TRANSCRIPT

A Force of OneAgile and the Solo Developer

Clint Edmonson, Architect Evangelist, Microsoft

Why are we alone?

What are we working on?

What do we need?

Do more with less!

Thanks Microsoft!

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?

Agile Practices

Intent Driven Development

BusinessValue

Vision documentUser storiesSingle project backlogCustomer contact

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

Single Project Backlog

Time ToMarket

ColocationRelative size estimatesSmall batch sizesContinuous integrationFrequent releasesResearch spikes

Relative size estimates (RELATIVE SIZE IS!)

Small batch sizes

Quality ToMarket

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

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

Simple design(YAGNI)

Simple design(YAGNI)

Visibility Single project backlogInformation radiatorsCustomer demos

Personal Kanban boardBacklog Work In Progress Done!

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

Pen

Backlog

Product Longevity

Coding standardsAutomated functional testsSustainable pace

Sustainable pace

Success Factors

Collaboration with customerAttention to qualityIncrementalismAutomationContinuous improvementEnergized workforce

Anti-patterns

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

Where do I start?

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

The role of tools

TFS vNext Cloud Preview

Try it out for free

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

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

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

Clint EdmonsonArchitect EvangelistMicrosoft

clinted@microsoft.com@clintedwww.notsotrivial.net

top related