Jack's Agile Notebook

264 Pages·2012·13.81 MB·English

Jack’s Agile Notebook
_
_
Last Updated 10 March 2015 _
_
Notebook Short Link: http://goo.gl/5IsK86 _
_
_
_ _!
_ _e
Jack Caine, SPC, CSM, CSPO, BSc. _ _er
_ _h
_ _

_ _e
_ _m
_ _
a
_ _
n
_ _
_ _r
_ _u
_ _o
_ _y
_ _
e
_ _
t
_ _i
_ _wr
_ _
: _e
[email protected] | Skype: CRhockey | (323) 580 - 6911 E _s
T _a
A _e
LinkedIn: http://goo.gl/xBdKRG _l
D _P
_
Blog: ​http://goo.gl/HWUSmu _
_
_
_
_
_
All information in this handbook can be found on the internet
Notebook Goals (My Agile Journey)
● Anti-Dogma (strengths, challenges, contrasts)
● Professional development through continued self-study
● Collection of ideas taken from smarter people than I
● Experience taken from the field
Funny / Useful Paradigm
USEFUL
FUNNY & USEFUL BUT
USEFUL NOT FUNNY
Y
N
Y N
N U
N F
U
T
F
O
FUNNY BUT NOT FUNNY &
N
NOT USEFUL NOT USEFUL
NOT USEFUL
Famous Quotes
“The one closest to the future has the best view” — Anonymous
“Be the change that you wish to see in the world.” — Gandhi
“We cannot solve our problems with the same thinking we used when we created them.” — Einstein
“In theory there is no difference between theory and practice. In practice there is.” — Yogi Bera
“The only good is knowledge and the only evil is ignorance.” — Socrates
“If you’re not confused, you’re not paying attention.” — Tom Peters
“We need to figure out a way to deliver software so fast that our customers don’t have time to change
their minds.” — Mary Poppendieck
“Most software problems will exhibit themselves as a delay.” — Alan Shalloway
“All truth goes through 3 stages. First, it is ridiculed. Second, it is violently opposed. And third, it is
accepted as self-evident.” — Arthur Shopenhauer (nicknamed “Obstinate”)
“Nothing happens until something moves.” — Albert Einstein
"Implement scrum and all the reasons
Boy: Do not try and bend the spoon. That's impossible.
that an organization has trouble
Instead... only try to realize the truth.
delivering a quality product on schedule
Neo: What truth? Boy: There is no spoon. Neo: There is no spoon?
are thrown up in your face, day after
Boy: Then you'll see, that it is not the spoon that bends, it is only yourself.
day, month after month - made obvious
and critical."
The Matrix (1999)
- Ken Schwaber
Topics
● Agile Principles ● Scrumban v. Kanban
● Lean Principles ● Scaling Scrum
● Key Concepts ● Agile Quality
● Scrum Roles ● Agile Engineering
● Scrum Meetings ● Agile Online Tools
● Scrum Assets ● Agile Coaching
● Definition of Done ● Team Training
● User Stories ● Metrics
● Estimation & Planning ● References
Why Implement Agile (For Teams)?
Create great products in a sustainable, flexible, fast and fun way
● Transparency - “Implement scrum and all ● Mastery - People want to do
the reasons that an organization has great work
trouble delivering a quality product on
schedule are thrown up in your face, day ● Autonomy - People want to
after day, month after month - made decide how to do their work
obvious and critical.” - Ken Schwaber
● Purpose - People want to
● Velocity - The best scrum teams in the understand the purpose of their
world average 750% gains over velocity of work and be part of something
waterfall teams with much higher quality, greater than themselves
customer satisfaction, and developer
experience.
Why Implement Lean-Agile (For Executives)?
Quicker ROI Containment/Decrease of Cost & Risk
● Decrease time to market (by building by ● Lower overall cost to deliver the product
MVP, MMF and MBI) ● Greater transparency into what is going on
● Prioritize work by cost of delay and business ● More visibility into the progress being made
value ● Learn earlier when projects are in trouble
● Increase the percentage of “done” projects (decide earlier to terminate or modify)
(since waterfall has such a large failure rate) ● Build the right thing the first time (by MVP &
● Show a quicker ROI through iteration MMF & MBI) - not enough resources for
● Build the right thing the first time (by MVP & everything
MMF & MBI) ● Have less rework (test first and build in
quality mentalities)
Better Client Relationships
● Be anti-fragile (Taleb’s concept of increasing
● Provide value to the customer
market variability that the organization can
● Meet commitments on time
tolerate)
● Shorter time to market
● Lower people cost through greater retention
● Improved quality
through better morale
● Decrease interruptions by support work
● Decrease process waste
● Quicker customer feedback, greater
transparency & better communication
Staged Releases = Quicker Cash Flow
Staged Releases
Break Even
w
o
l
F

h
s
a Single Release
C
Time
1st Release
Agile Manifesto
www.agilemanifesto.org
1. Individuals & interactions
over processes & tools.
2. Working software
over comprehensive documentation.
3. Customer collaboration
over contract negotiation. Note: “Over”
4. Responding to change doesn’t mean
over following a plan. “instead of”.
12 Agile Principles Behind Manifesto
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software/product.
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage.
3. Deliver working software/product frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout
the project.
5. Build projects around motivated individuals. Give them the environment
and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.