AZGiveCamp

https://meetup.com/azgivecamp

Software creators building great tools for local charities

Agenda

• Metrics

  • When and Why We Use Them

• Ceremonies

  • When and Why We Perform Them

• Tools & Technologies

  • When and Why We Implement Them

Metrics

Velocity Metrics Are Not For You!

Ways to Calculate Velocity

User Value (Product Perspective) Complexity (Engineering Perspective)

Story Points ≠ Time

Later Stories Leverage Earlier Implementations Different Implementer Experience Different Unknown-Unknowns Different Amounts of Tech Debt

What Are Story Points Good For?

Guide to how many points might be completable next iteration Warning to the team that something may need attention

Retrospective Red Flag

"We need to get better at estimating our work"

Test Coverage Metrics are not for You!

Good Coverage ≠ Good Tests

Good Unit Tests Give Us the Confidence to Refactor Ruthlessly

Unit Testing only the Happy Path

Metrics

• Velocity Metrics are not for you
• Test Coverage Metrics are not for you

Technical Debt - You Own It!

Technical Debt

Shortcuts now that have to be paid back later Lack of Supportability Lack of Maintainability Lack of Extensibility This is the work environment for your team Pleasant or Frustrating Fast or Slow Safe or Dangerous

Failure to Manage Tech Debt

is managing for the short-term Increases TCO Creates a bad work environment for devs

Tech Debt is Real $

Be Judicious about taking it on Add debt knowingly Track debt carefully Have a plan for repayment Pay it off regularly Communicate payback schedules Live up to those schedules

Metrics Take-Aways

• For the Dev Team to help themselves get better
  • Not for you to use to judge the team
• Be Careful How You Use
  • Velocity
  • Test Coverage
• Be Dilligent With
  • Technical Debt

Ceremonies

When and Why we Perform Them

Stand-Up Meetings are Not For You

Daily Stand-Ups

Devs making commitments to each other

Daily Stand-Ups

About Exposing Problems Quickly

Stand-Ups are Not

About Gathering Intel for Your Status Report

Iteration Planning Meetings are Not For You

Planning Meetings

About Understanding Stories

Planning Meetings

About Exploring Hidden Complexity

Planning Meetings are not

About Stuffing in Work

Ceremonies

• Stand-Up Meetings are not for you
• Iteration Planning Meetings are not for you

Retrospectives - You Own the Failures

Retrospectives

Retrospectives

Keep It Secret

Keep it Safe

Ceremonies Take-Aways

• For the Dev Team to help themselves get Better
  • Not for you to use to report up the chain
• Be Careful How You Use
  • Stand-Up Meetings
  • Planning Meetings
• Be Dilligent With
  • Overcoming Roadblocks

Tools & Technologies

When and why we use them

Task Boards are not for You

Who Needs an E-Board?

Task Board Purpose

What has been done? What needs to be done? What should be next? Is Anything Stuck?

Friction for Developers

Creating Value for Customers? Creating Reports for Management?

Prototypes & Research Spikes are Not for You

Spike

A Story used to reduce or eliminate unknowns in other stories

...the simplest thing we can program that will convince us we are on the right track... - Ward Cunningham

Prototypes & Spikes

Tools & Technologies

• Task Boards are not for you
• Prototypes & Spikes are not for you

Trust is Yours to Build or Destroy

Trust & Safety

"When a leader makes the choice to put the safety and lives of the people inside the organization first...remarkable things happen." - Simon Sinek TED: Why Good Leaders Make You Feel Safe

Estimates

Are Always Lies

Deadlines

Real Reasonable Responsible

Self Directed Teams

Make their own decisions

Call To Action

Use Retrospectives to create an environment of Trust for our teams

Eliminate anything from our process that doesn't lead to:

• Increasing value to our users
• Decreasing Total Cost of Ownership of our systems

This Slide Deck

http://DevTeamDreams.azurewebsites.net

Printable Version