welcome to our 5th annual uw techconnect conference · welcome to our 5th annual uw techconnect...

Welcome to our 5th annualUW TechConnectConferenceKey points to remember:v Networking event starts at 3:45 in the HUB Ballroom

v Use #uwtechconnect to connect on social

v Be sure to check-in with your Husky Card

Packing for an Agile Software Release: A Hiker’s Guide

With your tour guide: Dawn HemmingerEIIA Software Release Managerdmhemm@uw.edu | @dawnhemminger

1

2

3

4

5

Follow the Steps of our Journey

1

2

3

4

5

Organize

1

2

3

4

5

Organize: Everything in its placeEpic – A deliverable with a Purpose and Definition of Done that will require multiple stories to complete. Goal is to complete an Epic within a Release. Could also just be a container for themed work committed to a release, e.g. Reduce Tech Debt for Release 0.1.0

Story – A discrete piece of work with a Description and Definition of Done that can be standalone or support an Epic. Stories are sized to be completed within 1 sprint (2 weeks)

Bug – Defects in the product that are either discovered by the customer (labeled as such) or found internally. Bugs can be standalone or linked to other Stories and/or Epics.

1

2

3

4

5

Organize: Keep it up to date

1

2

3

4

5

Organize: Create a Staging Area

What’s a Release Plan and Why Have One?

> What? – A tool that communicates what features a team plans to deliver within

a fixed amount of time (scope or time-driven)

> Why? – Provides common vision about what needs to be achieved and when (Focus!)– Provides guidance in making decisions (Does this new work fit into the plan or can it wait?)– Helps prioritize work (Most important features are at the top of the plan.)– When done well, ensures that the team is delivering the highest value to customers on

schedule and within budget.

1

2

3

4

5

Schedule

1

2

3

4

5

Schedule: Understand the drivers

1

2

3

4

5

Schedule: Set goals

1

2

3

4

5

Schedule: Know availability

1

2

3

4

5

Learn from History

1

2

3

4

5

Learn from History: Know your Capacity

1

2

3

4

5

Learn from History: Identify Risks

1

2

3

4

5

Pack

1

2

3

4

5

Pack: Load the Release

1

2

3

4

5

Pack: Name the Release

1

2

3

4

5

Go

1

2

3

4

5

Go: Kickoff the Release

Field Notes

Now it’s your turn!

Essential Gear

> Atlassian Jira – Agile Software Project Management Tool> Atlassian Confluence – Wiki platform> Multiple Feature Cut Line Forecast Spreadsheet – Focused Objective> Single Feature Forecast Spreadsheet – Focused Objective> Team Capacity Calculator Spreadsheet – Stephanie Davis (@iamagile)> Agile Software Requirements – Dean Leffingwell

GOPACKLEARN FROM HISTORYSCHEDULE

A Hiker’s Guide

ORGANIZE

1 2 3 4 5

Earl Shaffer "Carry as little as possible, but choose that little with care.”