agile in short projects

0

Agile in Short Projects:A One Team Experience

1

How do we define short projects?

1 week to 2 months 1 or 2 person teams

2

What’s it like in the short duration, small projects world today?

3

Agenda

Background

2010 “A Pivotal Year”

Our macro group backlog

Inspecting and Adapting

Key takeaways

4

When we began…

5

RAD Global Coordinators

Europe CoordinatorsUS Coordinators

Onsite Technical PM (India)

Onsite Technical PM (Europe)

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

Developer

What the team looked like before…

6

Challenges

Developers lacked understanding

of big picture

Requirements would be lost by the time

they reached developers

Quality issues

Support done by developers

Changes in requirements, priorities &

timelines

Lack of a uniform way to communicate

with stakeholders

No cross sharing of knowledge within

teams in different locations

7

Agenda

Background

2010 “A Pivotal Year”

Our macro group backlog

Inspecting and Adapting

Key takeaways

8

Reorganizing the team

9

Brain-storming a vision

10

Our longer term vision

We deliver best in class service and

high quality solutions to our end users

The project experience will feel as

‘one team’

We build an exceptional pool of talent to draw upon

We provide a consistent experience

when delivering our projects

Adapt relevant

agile practices thatimprove upon service

delivery model

Our quality improves and

sponsors are delighted!

11

Let’s use a group backlog!

12

Agenda

Background

2010 “A Pivotal Year”

Our macro group backlog

Inspecting and Adapting

Key takeaways

13

A “macro” group backlog

As a user, I want to

define team roles

As a user, I want to communicated with

our end users consistently

As a user, I want to define how projects are

prioritized

As a user, I want to adopt relevant agile practices that make

sense to improve upon our service delivery

model

As a user, I want to define criteria

for SIAdevelopment

As a user, I want to define a

support process

As a user, I want to setup a process to

gather stakeholder's feedback on projects

14

The fruits of our backlog approach

15

What do team roles look like today?

SM/portfolio

POArchitect

Dev

Extended pool

PO Architect Dev

16

PO – Developer pairing:requirements

17

Our projects are more focused… what do we

take on?

18

Support is a separate entity

The development teams are

now dedicated and can finish

their commitments on time!!!

19

More

consis

tency

when

deliverin

g our m

essage…

20

Mini release plan

Sprint 1 (Nov 1)

Sprint 2 (Nov 8)

Sprint 3 (Nov 15)

Sprint 4 (Nov 21)

�GUI for filtering the reports�Tables with the same structures as current Access prototype�Data loads from existing Access db to local MS SQL tables�SQL server environment setup

�SQL stored procedures to return data for 6 reports �Logic for query to retrieve the data for 6 reports�UI ready for multiple reports in Excel (6 reports)�Aggregation level logic for reports (6 reports)�Script with all table structures (initial data load)�Performance testing of complex queries

�SQL stored procedures to return data for 5 reports �Logic for query to retrieve the data for 5 reports�UI ready for multiple reports in Excel (5 reports)�Aggregation level logic for reports (5 reports)�Scripts to load the Gross members data �Data load from Access to the Medical and Demographic Lookup tables �Performance testing of complex queries

�End to end integration testing �Mechanism for client to update state scenarios post initial load�Documentation for front end �Documentation for data model and data load scripts

Story Headline

21

Mini product backlog

22

Retro output

23

Agenda

Background

2010 “A Pivotal Year”

Our macro group backlog

Inspecting and Adapting

Key takeaways

24

What is working?

More transparency,

cross sharing and empowered

teams…

Clear roles

Direct contact with stakeholders

More consistency working with end users

Group & project sprint reviews

PO “Scrum of scrums”

Regular pipeline discussions

Group & project retrospectives

25

What can we improve?

Bring more consistency across all projects

Continue to focus on quality

Continue to bring transparency

Bring innovation to the way we work

26

Agenda

Background

2010 “A Pivotal Year”

Our macro group backlog

Inspecting and Adapting

Key takeaways

27

In summaryToday…

Before…

▪ Hierarchical structure▪ PMs empowered▪ Developers lacked

understanding of BIG picture▪ Many quality issues▪ Dev teams not dedicated to ‘just’

development▪ Changes in priorities, timelines

& requirements▪ The experience from the client

changed depending who they work with▪ Lack of a uniform way to

communicate with stakeholders▪ No cross sharing of knowledge

within teams

▪ Flat structure

▪ Entire team is empowered

▪ Developers understand & contribute to vision

▪ Higher quality apps

▪ Support separate entity

▪ Projects are time-boxed

▪ More uniform experience with clients

▪ More cross sharing of knowledge

28

Key takeaways…

Our macro backlog is a way to ensure we make baby steps towards our grand vision

Focus on starting small and try ideas out with a few projects (hence why the stories in our macro backlog are helpful)

Experiment, be patient, be open to change and expect things won’t work and you have to move on to the next thing

Ensure the team believes!

29

Q&A

Yvannova_Montalvo@mckinsey.com

Jyoti_Prakash_Datta@mckinsey.com

30

References

�prince2-small-projects.jpg. Sep 23, 2007. Prince 2 Training Website. Web. 16 Jan 2012. Retrieved from http://www.prince2training-uk.org/using-prince2-in-small-projects�istock_puzzle-businessman.jpg. Apr 1, 2008. Sherman Capital Advisors. Web. 16 Jan 2012. Retrieved from url http://shermancapitaladvisors.com�Vision.jpg. The Attraction Institute. Web. 16 Jan 2012. Retrieved from urlhttp://attractioninstitute.org�lightbulb-idea-124411-05112010-124411-05112010.jpg. Business Opportunities Weblog Network. Web. 16 Jan 2012. Retrieved from url http://www.business-opportunities.biz/2010/05/11/is-my-business-idea-a-good-one/�Focus_Group.jpg. Web. 16 Jan 2012. Retrieved from url http://getpaidcentral.com�CLIPART_OF_15195_SM_2.jpg. Adoptive Families Associations of BC. Web. 16 Jan 2012. Retrieved from url http:// adoptionsupportinterior.blogspot.com