Agile Scrum what s in a name Meet your presenter

Agile/Scrum what’s in a name… Meet your presenter Randy Schmidt, PMI-ACP|CMS | MCP Strategic “Results” Architect

Agenda Overview - Why bother Small iterative ‘deliveries’ SCRUM Kan. Ban – XP Summary notions Next Steps-Call to Action

Overview for this presentation • I hope to leave you with “Three main points” – AGILE: • “It just works” – we’ll look at why • “Scrum” leads agile methodologies by an overwhelming % - we’ll build a scrum team • “Not just for software development anymore”… - any project can use the benefits of Agile - You decide on ANY takeaways

Why Bother – not just according to Schmirk • Requirements based acquisition (especially) IT is “hard – broke” • 6 out of 10 – dead on arrival, 4 remaining 2 are late or over budget, and 1 has ill-defined USER requirements = 10% for the last 30 years • 2010 Pew showed only 15% of all IT projects succeed in not being over budget, time or both • Standish’ 09/Sauer’ 07 determined that any project over ~$1 million has only 25% chance of success (on-time, on-budget, meets original business need)

Session’s law of size - 2011

http: //www. agilemanifesto. org

Small Iterative Deliveries • Collaborative – End User (Product Owner) Developer and Tester • 1 st set of features or components is as little as two weeks • Continuous delivery of ‘shippable’ capabilities • Not a single “requirement” in the mix - more like “desirements” after short term demos

SCRUM – Kan. Ban - XP • (Scrum Master bias) if AGILE is the “neighborhood”; e. Xtreme Programming(XP) Kan. Ban and several other ‘cul-de-sacs’ vs the SCRUM ‘community club house and pool’… • SCRUM – 10 simple items TOTAL! • 3 roles, 4 [time-boxed] meetings, 3 artifacts • Product Owner, the TEAM and the SCRUM Master • Sprint planning[1 hr], daily Scrum[15 min], Retrospective[1 hr], Backlog grooming [continuous] • Conventional ‘thought leadership’ applies, stakeholders, project/program management provide the Vision, Mission, Goals and Objectives through a rechartering event following the 2/4 week “demo”

Summarize over-arching Agile notions • A Chicken and a Pig wish to open a breakfast diner… • “Committed” versus “involved” • EPICS, Components, User Stories, Tasks to provide deliverable features & functionality - incrementally • User Story examples: where the realm of the possible meets the practical (3 x 5 cards) • • AS : who I NEED TO: what capability SO THAT I CAN: when, where, metric parameters (on the back)I Know we are done: how , to what standards of measurement

Speed to Value AGILE Other Methodologies Pros+ Cons- incremental and Early delivery non typical iterative contracts requirements based contracting Delivery all at once code/project hard on the (s) that work Product Owner plenty of rigor & documents Delivery all at once features in weeks transparent w/daily burn nontransparent Features in months/yrs less rework just in time not a silver bullet ok to fail Rigid Designs less flexible 10 -25% success

Next Steps – Call to action • Let the Scrum Begin… • Standing at or near the Info Radiator • 15 minutes, Only the headlines, What did I do, what am I going to do, what’s in my way • AGILE/CMMI/Waterfall/are more powerful when they co-exist • Pioneers vs indigenous • “Cowboys” and “Indians” • Agile that scales – webinar at noon/next slide Help evangelize, so that contracts being written include notions & metrics of Agile

Scaled Agile Framework™ Big Picture