Agility primer
31
-
Upload
dmitry-sharkov -
Category
Software
-
view
133 -
download
0
Transcript of Agility primer
TODAY'S AGENDA
How did we get here?What agility means to usPhilosophy behind agile developmentWork culture and agilityRoles in agile developmentFollowing the principlesBeyond process - people and toolsAn example approachMeasuring successRevisiting our purposeQ & A
WHY ARE WE TALKING ABOUT AGILE DEVELOPMENT?
Because it beats the alternative?
Because developers, customers, and everyone in-between has found it makes them happier.
Because developers, customers, and everyone in-between has found it makes them more successful.
THE FAILURE OF WATERFALL SHOULD NOT COME AS A SURPRISE.HTTP://WWW.MOUNTAINGOATSOFTWARE.COM/BLOG/AGILE-SUCCEEDS-THREE-TIMES-MORE-OFTEN-THAN-WATERFALL
WHY ARE WE TALKING ABOUT AGILE DEVELOPMENT?
Success: on budget, on time, with all planned features
What is AGILITY?
The ability to change[direction] efficiently.
In software development, it also includes a philosophyaround making people as productive as possibleregardless of the need for frequent or sudden change.
Change is inevitable
Must the cost of change riseexponentially as time passes?
Fight change and it will.
Enable change through agility.432 PARK AVE
SNOWBIRD, UTAH
WHAT
WHEN WHEREFEBRUARY 2001
THE AGILE MANIFESTOAND THE PRINCIPLES BEHIND IT
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have
come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
THE AGILE MANIFESTO
1 - Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2 - Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3 - Deliver working software 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.
PRINCIPLES BEHIND THE AGILE MANIFESTO
7 - Working software is the primary measure of progress.
8 - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9 - Continuous attention to technical excellence and good design enhances agility.
10 - Simplicity — the art of maximizing the amount of work not done — is essential.
11 - The best architectures, requirements, and designs emerge from self-organizing teams.
12 - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
PRINCIPLES BEHIND THE AGILE MANIFESTO
BUILDING TRUST
SHARING OWNERSHIP
WORKING����������� ������������������ TOGETHER
REMOVING����������� ������������������ OBSTACLES
DOING����������� ������������������ VALUABLE����������� ������������������ WORK
MY "SIMPLE" AGILE PRINCIPLES
ELIMINATING RISK
MY "SIMPLE" AGILE PRINCIPLES
TRANSPARENCY
EMPOWERMENT
9 P
Know what 100% of the
team is doing 100% of the time. Communicate.
Trust each other to be great. Eliminate obstacles to success. Let teams self-manage. Give everyone
the tools to be the best they can be.
This����������� ������������������ is����������� ������������������ a����������� ������������������ big����������� ������������������ culture����������� ������������������ change
Trading old values and old approaches for new.
Business and client-centrism Self-managing teams Servant-leadership Focus on value delivered
ROLES IN SOFTWARE DEVELOPMENT
ROLES IN SOFTWARE DEVELOPMENT
• DEVELOPMENT TEAM - Cross-functional; testing, coding, database work, design - all skills present, ideally.
• PRODUCT OWNER (or proxy) - Fully engaged with theteam. Responsible for maximizing ROI. Decides priorityof work and understands the business needs and values.
• PROCESS MANAGER - Helps the team work towardsincreased agility, build good habits, and evolve amethodology. Coaches to the agile principles.
• PROJECT MANAGER - Empowers the team to be asproductive as possible. Mentors and guides. Helpsresolve obstacles and escalate issues of risk.
Following the Principles
TRANSPARENCY
Following the Principles
DOINGVALUABLE
WORK
BUSINESS CENTRIC
Following the Principles
ELIMINATINGRISK
REDUCINGWASTE
Following the Principles BULDING
TRUSTWORKINGTOGETHER
SHARINGOWNERSHIP
Following the Principles EMPOWERING DEVELOPERS
Following the Principles CONTINUOUSLY
IMPROVING
TYING IT TOGETHER…SCRUM
TYING IT TOGETHER…SCRUM EVENTS
•Daily Stand-Up •Sprint Planning •Sprint Review •Retrospective
SCRUM PROVIDES SCAFFOLDING
Track work remaining Measure pace Make a commitment Write the software Test the software Document the software Define 'DONE' Measure success
IT DOES NOT DICTATE HOW TO…
Beyond Process
MEASURING SELF-IMPROVEMENT
Velocity Regression count Predictability Clarity of goal Stability Self-management Team happiness
MEASURING SUCCESS
Business value / time Production defects Average cost of defects On-time delivery Team happiness
AGILITYWRAP-UP
