4. An agile approach
• Introduced to scrum/agile in May 2013
– Trained team on scrum in June 2013
– Started sprint 1 on June 27, 2013
– First release for user testing Dec 20, 2013
– Production release June 15, 2013
• Had set goal of “code on the ground” in one
year in Jan 2011
– Traditional project management (waterfall) didn’t
work
7. What is Agile development?
• Iterative and incremental
• Requirements and solutions evolve
• Collaborative and self-organizing
• Adaptive planning
• Time-boxed approach
• Responsive
• Yes, there’s even a MANIFESTO!
– Individuals and interactions over processes and tools
– Working software over comprehensive documentation
– Customer collaboration over contract negotiation
– Responding to change over following a plan
10. Highlights of Scrum
• A framework – not a silver bullet
• Rugby (scrimmage) – put the ball into play
• Values
• Benefits
• Impact
• MVP (lean approach)
• Process
15. Minimum viable product
• New search interface (web client)
– CAS support
– Responsive design
– Brand alignment
• New repository
– XML standard
– Robust metadata
– Live sync with Bell
20. Resources
• Local agile interest group agile-
development-l@iu.edu
• Hundreds of people across 1ITIU now
adopting it
• http://www.scrumguides.org/
• https://www.scrumalliance.org/
21. Resources
• Lots of books, even on Books 24/7
• Agile product ownership in a nutshell -
https://www.youtube.com/watch?v=502ILH
jX9EE
• Cynefin framework (problem spaces)
https://www.youtube.com/watch?v=N7oz3
66X0-8
• Chuck Aikman – caikman@iu.edu
Editor's Notes
Poll the audience… break the ice…
How many saw the lunar eclipse this morning?
How many have heard of agile? Scrum? Kanban? XP?
How many are developers?
How many are project managers? Product owners?
Why change? Houston, we have a problem… it IS broken!
Trying to comprehensively solve complex problem holistically will give you (and everyone around you) ulcers! You can’t turn the Titanic quickly…
Do you want to succeed or fail?
Intro – purpose of session – sharing how this process helped salvage the project of building a replacement for the KB. Adopting agile was like the dawn of a new day.
On June 27, 2013 we started our first sprint! One year and 25 sprints later, we had finally executed on the goal of “code on the ground in a year” (a goal initially set in Jan 2011 – by the way).
Once we focused, adopted scrum, and started sprinting — that all changed! In fact, we shared the STG URL out to the Support Center and Client Services and Support managers on Dec 20, 2013 – less than 6 months! That was “code on the ground” — we had working software that we had enough confidence in, to allow testing.
As you all know, we went production on June 15, definitely making production in less than one year.
It is also significant that in the first year of Scrum and being agile, that over 100 training seats for CSM or CSPO have been conducted here at IU, and we’ve been able to spread the discussion of agile development within the organization, and the university.
Forces you to chunk the work – eating the elephant one piece at a time
Many characteristics
Many, many resources available
The problem with complex problems
We deal with complex problems, and many unknowns
Best method for complex problem space? Probe-Sense-Respond (repeat)
In a nutshell…
More than one flavor of facilitating agile…
We chose Scrum!
A framework
Not a silver bullet
Not for every problem
Define
Overview
Explain how it impacted our thinking on KMS
Flipped it inside out
Deliver value to most customers first
Eat away at the elephant
What it looks like
Daily scrum (reset – put the ball into play)
What did you do yesterday?
What are you going to do today?
What impediments?
Scrum Master is servant leader – enable success, don’t dictate
Broad adoption throughout 1ITIU
Scrum/Agile brown Bag Series
