Scrum without the Sugar Coating

You want me to do what?!

Introductions

Panel members/roles Gigi Zenk– Sponsor Dianne Foster- Developer Ben Hopkins– Developer Ann Deuell– Analyst Chad Baker– Tester Irene Hill– Product Owner Melodi Cottongim– Scrum Master Mara Tallman– Scrum Master

Agenda

How we got started Q&A (10 minutes)

Scrum process at DOL Q&A (7 minutes)

Outcomes & what we’re doing now Q&A (15 minutes)

When we started Scrum

Summer 2011 – training (6 PM’s, analysts)

2011 Nov/Dec/Jan 2012–2 teams, training, coaching, working

How we got started with Scrum Executive and staff interest Articles from CIO Curiosity in the Project Office

How we got started with Scrum Forced ‘opportunity’ Project – impossible timeframe for

Waterfall

How we got started with Scrum Formed team Hired Coach, trainer

How we got started with Scrum Team training in 3 hour blocks over

six week period Parallel to planning and running

Sprints

How we got started with Scrum Professional coach on-site 80 hours

Coaching spread over 3 months Helped with▪ Planning▪ New ways of working▪ New ways of communicating, collaborating

Misconceptions getting started Misconception:

No documentation, no need to do architecture planning

Misconceptions getting started Misconception: Release every sprint

Reality: It will take a while (several months) before you Might need a release every sprint

Misconceptions getting started Misconception:

Must have software tool to manage Scrum

Reality: Until you have your process running smoothly, a tool will get in the way

Misconceptions getting started Misconception: Agile/Scrum is

flexible, fluid we can do things however works for us

Reality: Scrum is a disciplined, and specific process

Barriers getting started Getting enough

time from team members

Changing team members

Barriers getting started

Product owner – big cultural shift of accountability

Confusion on roles of PM’s, analysts, product owners

Q&AHow we got started

Scrum Process at DOL

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

RolesSCRUM TEAM Analyst Designer Developers Testers UAT Testers Scrum Master Product Owner

STAKEHOLDERS Sponsors Steering Committee Product Users IS Supervisors Architects DBA Configuration

Management

Form a Team

Create a Roadmap

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

Create a Roadmap

Sprint Planning

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

Sprint Planning

1. Team members provide available hours for next sprint.

2. Team pulls in stories by priority, decomposes the stories into tasks, team members volunteer to complete the tasks and assign hour estimates.

3. Analyze the plan: fill in gaps and adjust workloads.

4. Team commits to delivering the sprint backlog.Save 20% of available hours.

Sprint Work

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

Sprint WorkTASK BOARD BURN DOWN

CHART

15 Minute Daily Stand Ups

Backlog Grooming

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

Feedback Incremental Release

2 Week Cycle

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Backlog Grooming

CREATE STORIES PRIORITIZE BACKLOG

Story Time = Team Communication

Demo

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

DemoBURN UP CHART COMPLETED STORIES

Incremental Releases

Retrospective

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

RetrospectiveFACILITATED ACTIVITY ACTION PLAN

Continuous process improvement

Re-start the Cycle

1. Product Roadmap

2. Release

Roadmap3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog

Grooming

4a Daily Stand Ups

4b Complete

Tasks

Feedback Incremental Release

2 Week Cycle

Let’s see a team in action…

Q&AScrum Process at DOL

Outcomes

Dedication and loyalty to team grew quicker than expected

Outcomes

Accomplishing what didn’t seem possibleIn a timeframe that

didn’t seem possible

Requirements current, accurate, just in time

Outcomes

Collaboration, breaking down barriers between roles

Improved communication

Outcomes

Desire for informal training in the agency

Monthly lunch and learn sessions on Scrum

Outcomes

Cultural shift – drive to expand and have more Scrum teams is coming from the ground-up.

People WANT to participate.

Lessons learned – why first two projects succeeded Hiring coach for first two projects

prevented failure, gave team confidence

Project sponsors and executives provided 100% support

Initial teams were had people who wanted to participate

Authority and responsibility was enabled at all levels

Dedicated room/walls for planning, meeting

What we’re doing now

Training 40 more IT staff

What we’re doing now

Forming more permanent Scrum teams

Teams formed around products for all work coming in

What we’re doing now

Consultant for forming the new teams

Internal coaches

What we’re doing now

Contractor’s working within our Scrum teams

Contract deliverables – sprints

What we’re doing now

Trying Team Foundation Server – for Scrum

Q&AOutcomes and what we’re doing now

Thank you for your time

1. Product Roadma

p

2. Release Roadma

p3. Sprint Planning

4. Sprint Work

5. Demo

6.Retrospective

4c Backlog Groomi

ng

4a Daily Stand Ups

4b Complete Tasks

Feedback Incremental Release

2 Week CycleProduct Roadmap Product owner describes the marquee features, sequences them in priority order.

Release Roadmap Scrum Master facilitates feature t-shirt sizing poker with team and product owner groups into releases.

1 2

Sprint Planning Team provides availability, breaks top priority stories into tasks, and teammates volunteer for tasks.

3 Stand Ups 15 minute team chat: state tasks done yesterday, plan for today, identify roadblocks.

Complete Tasks Work tasks, help teammates and maintain task board: move tasks into doing or done and update remaining hours.

Backlog Grooming Analyst facilitates story creation workshop, Scrum Master facilitates story time point sizing, and Product Owner prioritizes the stories.

4a

4b

4c Demo

Product Owner describes the business value and team demos the functionality only for stories that meet ‘done’ criteria. Product Owner collects feedback.

5 RetrospectiveScrum Master facilitates discussion about what went well and things to improve. Team commits to an action plan.

6

DOL Scrum Process