An introduction to agile sw development, exploring the why, how and what. But is sth missing? Seems that successful agile transformations require an agile mindset….
As presented in the 1st Lean&Agile meetup @ thessaloniki, March 2014
3. SOFTWARE FOLKS
DISTRESSED BY THE
CONTINUAL DILUTION
OF THEIR ENERGY
COMMITMENT AND
TALENTS, CAUSED BY
DYSFUNCTIONAL
WAYS OF WORKING,
DYSFUNCTIONAL
MANAGEMENT,
DYSFUNCTIONAL
CLIENTS,
TOOK MATTERS INTO
THEIR OWN HANDS
AND…!!!!!
Bob Marshall
4. !
BACK IN 2001 SEVENTEEN
“LIGHTWEIGHT
METHODOLOGIST” GOT
TOGETHER IN A SKI
RESORT IN UTAH - THEY
NAME THE NEW
MOVEMENT “AGILE” AND
THE AGILE MANIFESTO FOR
SOFTWARE DEVELOPMENT
WAS BORN.
UNCOVERED
BETTER WAYS
OF DEVELOPING
SOFTWARE
BY DOING IT
AND HELPING
OTHERS DO IT
6. INDIVIDUALS AND INTERACTION
OVER FOLLOWING A PLAN
WORKING SOFTWARE
OVER COMPREHENSIVE DOCUMENTATION
CUSTOMER COLLABORATION
OVER CONTRACT NEGOTIATION
RESPONDING TO CHANGE
OVER FOLLOWING A PLAN
AGILE
ESTABLISHED
BY FOUR
VALUES
THAT IS, WHILE THERE IS VALUE IN THE ITEMS ON THE
RIGHT, WE VALUE THE ITEMS ON THE LEFT MORE
7. SATISFY THE CUSTOMER THROUGH EARLY
CONTINUOUS DELIVERY
WELCOME CHANGING REQUIREMENTS, EVEN LATE
DELIVER WORKING SOFTWARE FREQUENTLY
BUSINESS PEOPLE AND DEVELOPERS
COLLABORATE DAILY
BUILD PROJECTS AROUND MOTIVATED
INDIVIDUALS
CONVEY INFO VIA FACE-TO-FACE CONVERSATION
PRIMARY PROGRESS MEASURE:WORKING
SOFTWARE
CONTINUOUSLY DEMONSTRATE TECHNICAL
EXCELLENCE
SIMPLIFY:MAXIMIZE AMOUNT OF WORK NOT DONE
SELF-ORGANIZE
RETROSPECT AND TUNE BEHAVIOUR
AGILE
GROUNDED
BY TWELVE
PRINCIPLES
8. RELATIVE ESTIMATION, SIZE-BASED (POINT) ESTIMATION, PLANNING
POKER, GROUP ESTIMATION
PRIORITISED PRODUCT BACKLOG
USER STORIES, STORY MAPS / MMF, STORY SLICING, ACCEPTANCE TESTS
SHORT ITERATION, WIP LIMITS
EARLY AND FREQUENT RELEASES
ROADMAPPING VELOCITY-BASED
PLANNING AND COMMITMENT
ITERATION PLANNING / ITERATION BACKLOG RELEASE PLANNING /
RELEASE BACKLOG
TIME BOXED ITERATION
PAIR PROGRAMMING, CONTINUOUS INTEGRATION
RISK BACKLOG, TEST AUTOMATION,
PULL-BASED SYSTEMS, BURN UP/BURN DOWN CHARTS
!
SCRUM, XP, DSDM, CRYSTAL, FDD, ASD, YOUR
OWN FRAMEWORK
AGILE MAKE
USE OF
DIFFERENT
PRACTICES
10. STATE OF AGILE SURVEY
(2010-2012)
FASTER TIME TO MARKET
ENHANCE ABILITY TO
MANAGE CHANGING
PRIORITIES
IMPROVE PROJECT
VISIBILITY
ACCELERATE TIME TO
MARKET
INCREASE PRODUCTIVITY
ENHANCE SW QUALITY
REDUCE RISK
SIMPLIFY DEVELOPMENT
PROCESS
IMPROVE TEAM MORALE
MANAGE DISTRIBUTES
TEAMS
REDUCE COST
15. FAILURES
COMPANY
PHILOSOPHY OR
CULTURE AT ODDS
WITH AGILE VALUES.
EXTERNAL PRESSURE
TO FOLLOW
WATERFALL
PROCESSES.
BROADER
COMMUNICATION
PROBLEM.
FAILURE TO
INTEGRATE THE
RIGHT PEOPLE
AND TEACH TEAM
BASED CULTURE
17. IF THERE IS ONE
THING AGILE HAS
BROUGHT TO THE
TABLE IS THE
REALISATION OF
HOW IMPORTANT
THAT “FLUFFY
PEOPLE” STUFF IS
AND HOW WE
NEED TO PAY
ATTENTION
!
!Linda Rising
19. THE MINDSET
DETERMINES OUR
GOALS,
OUR REACTION TO
FAILURE,
OUR BELIEF ABOUT
EFFORT AND
STRATEGIES,
OUR ATTITUDE
TOWARDS OTHER’S
SUCCESSFUL
THERE ARE TWO TYPES
OF MINDSET
FIXED&AGILE(GROWTH)
20. FIXED MINDSET
ABILITY IS STATIC.
GOAL IS TO LOOK
GOOD.
AVOID CHALLENGES.
FAILURE DEFINES
THE IDENTITY.
EFFORT IS GOOD
BUT FOR THOSE
WITH NO TALENT.
REACTION TO
CHALLENGE-
HELPLESSNESS
21. AGILE MINDSET
ABILITY CAN GROW.
GOAL IS TO LEARN.
EMRACE
CHALLENGE.
FAILURE PROVIDES
INFORMATION.
EFFORT IS THE PATH
TO MASTERY.
REACTION TO
CHALLENGE -
RESILIENCE
25. REMEMBER
THAT THE MOST
IMPORTANT THING
TO KNOW ABOUT
AGILE METHODS OR
PROCESSES IS THAT
THERE IS NO SUCH
THING.
THERE ARE ONLY
AGILE TEAMS.
THE PROCESSES
DESCRIBED AS
AGILE ARE
ENVIRONMENTS FOR
A TEAM TO LEARN
HOW TO BE AGILE
!!!
www.agile-process.org
26. REMEMBER THAT
AGILE IS NOT A SILVER
BULLET.
AGILE THAT WORKED
FOR SOMEONE IT
DOESN’T MEAN IT WILL
WORK FOR YOU.
LEARN AND FOLLOW
RULES.
BREAK THEM.
MAKE YOUR OWN.
LEARN LIKE A
SCIENTIST
-INSPIRATION
-EXPLORATION
-TESTING
-COLLABORATION
-EXPLOITATION