Lean/Agile Development Successes and ChallengesJill YetmanProject Team Lead / Product Managerjyetman@uw.edu

PAINT THE FENCE

Jeff Gothelf

LEAN / AGILE OVERVIEW

> AGILE/SCRUM – 2 week sprints & 3-4 hour planning meeting every two weeks

– User stories & acceptance criteria

– Estimate the complexity, not the hours

– Respond to change

> KANBAN “White board”– Use of board to show work

(To do, Specify, Execute, Verify, Done)

– Limit work in progress

– Explicit Policies

TEAM TOOLS

> Physical board & JIRA for 3+ years

> Recently moved to JIRA Greenhopper board

> Daily stand-ups & planning meetings every 2wks

> User stories > acceptance criteria

> Zephyr plug-in for JIRA to track manual tests

> Crucible for code reviews

> Cucumber for test automation

THE MYPLAN TEAM

> Product Owner with Advisory Group

> Registrar, Advising, 1st Year Programs, Grad School

> 1 Project Lead / Product Manager

> 5 Devs: Dev Lead, 2 Java Devs, 2 UI Devs

> 3 Business Analysts

> 2 Test: Test lead, 2 student manual testers

> 2 User Experience Designers

> .5 Technical Architect

SUCCESSES

PROCESS

> Adopted and adapted a Lean/Agile process for our team

> Frequent and regular releases

> Responded to emergent priorities quickly

PRODUCT

> Huge adoption rates after improving registration hand-off

> Advisers and departments have required use of MyPlanto improve conversations

> UG, Grads, UWEO, Bothell/Tacoma, CTCs

Has the student planned any

active sections?

Is the TS published for the quarter planned?

How many primary/secondary sets are planned?

Do all planned sets have the same H,

W, and credit attributes?

Is the section offered for a single value?

System passes course and

details from the section profile

Yes

Student selects a section profile (available combination of credit, H, W) from planned

section sets

No

> 1only 1

System passes specific section ID

Yes

Is the course offered for a single

value during the planned quarter?

System passes course details from planned

quarter version (credit, AoK, GenEd)

Student indicates # of credits based on section details

System passes section ID and

selected credit value

Student indicates # of credits

(based on planned quarter version)

System passes course details from planned quarter version and selected credit value

No

No

Yes

No

How many sections are

offered?

NoDo all non-honors offered sections have the same

writing and credit attributes?

>1Yes

only 1

System passes course and

details from the section profile

Yes

Student selects a section profile

(available combination of

credit & W)

No

IGNORE LISTSystem captures

non-offered courses, doesn't

send them to plan audit, but sends

them to the hand-off screen to let student know

YesIs the course

effective during the quarter it's

planned?

IGNORE LISTSystem passes

course to ignored course list

No

Note: By default, the system should pass non-honors, non-CR/NC sections.

Yes

Plan Audit Hand Off Screen Logic Creator: Jill Yetman | Modified: Wed Jun 19 2013

CHALLENGES

> Doing what's “right” vs. what's we promised– User-centered design vs. project timeline

– Anticipated vs. emergent needs

> Frequent releases vs. hardened service– Complex system with frequent changes

– Load, response, and integration testing

> Team size: focus vs. breadth– Awareness across system

> Holistic vs. incremental design– Scaling your initial design decisions

– Watching out for break points

> Tasks vs. the individuals

QUESTIONS