1. David Mann
SVP & CIO
(714) 606-9356
AgileChief@gmail.com
© Copyright 2014

2. Agenda











Introduction
Value Proposition
Process
Commitment
Dependency
Constraints
Non-Customer Focus
Process Components
SCRUM – Agile Process
TED Talks
Q&A

3. Introduction
Our Theme:
Time to
Grow

4. Introduction
What is the definition of insanity?
 Doing the same thing over
and over and expecting
different results!

5. Introduction
Implementing
industry’s best
practices and
processes
IT Process

6. Value Proposition
Technology as a Key Differentiator
•
•
•
•
Sales Efficiency
Enhance Customer Experience
Increase Staff Loyalty
Beat the Competition
Accelerate Growth

7. Process
The most important thing about
Process is to have one




FOCUS – Wildly Important Goals
LEAD MEASURES
SCOREBOARD
CADENCE of ACCOUNTABILITY

8. Process
Why a Process?
• Time to Market
• Productivity & Efficiency
• Quality
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
Functionality
Security
Compliance
Scalability
Expandability
Maintainability
Availability
Accessibility
Visibility
Intelligence

9. Process
People DO NOT follow complex processes!

10. Process
Essential Elements of A Process:
 Simple
 Industry Proven Practices
 Customizable
 Scalable
 Popular (think resources)
 FREE

11. Process
SCRUM – Agile Process Methodology

12. Process
What is Agile about?
 Agile is about change
 Agile is about customer involvement
 Agile is about focus
 Agile is about lead measures
 Agile is about scoreboard
 Agile is about accountability
“The only constant in the universe is change”
12

13. Process
What is Agile about?
Plan
QA/Stabilize
Envision
Build
Deploy
Agile has tracks not phases; teams dash to the finish-line without waiting for each other
13

14. Process
 Agile is not about rushing things; but if Agile is applied things gets
delivered faster with higher quality. Why?
• Short Sprints (iterations) - 2 to 4 weeks
• Full Customer Involvement to adjust course
• Frequent Releases & Check-Points
• Multi tracks
• Focusing on delivering software (not process)
 Agile does not mean chaos:
• Agile has “change control“ after each sprint (but less formal)
• Agile has meaningful short documents; prototypes clarify requirements and design; projectroom eliminates hefty documents and long meetings; the team focuses on delivering quality
software and not documents
14

15. Commitment

16. Dependency
Quality
Scope

17. Dependency
Honey,
Can we just add Sure Sweetheart,
Let’s make baby! done
and
resources anda get it But it takes a lady 9
I wantin 1 by next months to make a baby!
it month? month

18. Non-Customer Focus
How athe consultant
Matt, Zaven, and
How thethedeveloper
How IT Operations
Whatthe architect
How SME explained
customer
How business analyst
Keith were billed
programmed it
really neededit
documented
describedit
designed it
it
installed

19. Milestones
Process Components
Build

20. Deliverables
Process Components
Production
Release
PDD
UAT
BRD
Rollout
Plan
TDD
Build
Code
Test
Plan

21. Team
•
•
•
•
•
•
Foster open
communication
Work toward a
shared vision (focus
on delivering
business value)
Empower team
members
Establish clear
accountability
Stay Agile and
expect change
Partner with
customers
Process Components
Release
Manager
Business
Analyst
Sponsor
Customer
Architect
Tester
Developer

22. SCRUM – Agile Process
Focus
1.
2.
3.
What did you do yesterday?
What will you do today?
Do you have any road-blocks?
Lead
Measures
Scoreboard
Cadence
Account
-ability

23. SCRUM – Agile Process

24. TED Talks
Bruce Feiler:
Agile Programming for your family
http://www.ted.com/talks/bruce_feiler_agile_programming_for_your_family.html

25. Q&A
David Mann
SVP & CIO
(714) 606-9356
AgileChief@gmail.com
© Copyright 2014