winnipeg agile users group march 10 2011

Post on 13-Nov-2014

1.032 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

IT is Too Darn Slow!

TRANSCRIPT

Iteration 1w/ Doug & Steve

Introduce yourselves

• Name• Company• Role• Agile Knowledge Ranking:– Teacher– Student– Rookie

The Game

• Ball Point Game– Pass as many balls as possible through every team

member– 1 point for each ball passed through entire team

• Rules– Hands Only– Each ball must have air time– No ball to your direct neighbour– Start Person = End Person– Iteration = 2 minutes

Round 1

So What?

• IT is Too Darn Slow (InformationWeek article)

• “If IT's too slow, business is too slow to innovate. It's that simple.“ – Chris Murphy

Article from InformationWeek:http://www.informationweek.com/news/global-cio/interviews/showArticle.jhtml?articleID=229218781

So What?

• “This need for speed is about shortening the distance between a great idea and the end result”

• HP CIO “has cut the time it takes to complete the typical HP IT project down to six months, but now he thinks he needs to slash it again, to three months.”

Round 2

• Goal: Double your speed

• 3 Minutes:– Discuss ways to improve– Reflect upon and challenge your process and your

constraints

Rounds 3 +

Discussion

So What? (part 2)Alan Shalloway (@alshalloway)10-12-02 8:01 AMEliminating delays between what you do gives you a better return than getting better at what you do

Matt Barcomb (@78mgb)11-03-09 12:48 PMOH: “agile is about doing more of what works and less of what doesn’t” – yes! Both are required!

Back to InformationWorld Article: “shortening the distance between great idea and end result”

So how does this relate to agile?

• Focus on reducing hand-offs– Dedicated teams– Co-located teams

– Eliminate Requirements, Design, Develop, Test “phases”.

So how does this relate to agile?

• We calculate and track our Velocity– Difficult to measure improvement without it– Not tasks; user stories. – Not tables,

screens or services; delivered functionality

– Working Code (“done”)

So how does this relate to agile?

• Continuous Improvement (Frequent Retrospectives)

– Stop & reflect regularly in order to speed up– Embrace Experimentation– Fail Fast (Learn Fast)

– What can we do to go faster?

So how does this relate to agile?

• Cross Functional Teams– Get everyone involved in all aspects of the solution and

process – not just PM, Architect, QA, UX Designer, “the smart person in the room”

“If you want to go fast, go alone. If you want to go far, go together.” – African proverb

Material List

• Presentation details, game info, links etc can be found at http://www.agilewinnipeg.com/

Next up… Agile Fishbowl

Thank you!– Doug Kok

@dougkok

– Steve Rogalsky @srogalskyhttp://winnipegagilist.blogspot.com/

Prize Draws

Thank you!– Doug Kok

@dougkok

– Steve Rogalsky @srogalskyhttp://winnipegagilist.blogspot.com/

top related