2017 - jitf - agile survival kit - how to save the marriage
Post on 15-Apr-2017
67 Views
Preview:
TRANSCRIPT
JUMP IT FORUM 2017 ZAGREB
HOTEL & CONGRESS CENTER ANTUNOVIC | APRIL 11-12, 2017
Tuesday, May 2, 2023 JUMP IT FORUM 2017 ZAGREB 3
OUR RECENT AGILE COACHING ENGAGEMENTS
CONFERENCE DISCOUNT TODAY
CHAPTER ONE - “CHAOS REPORT”
be the problem?
What seems to
In come the Japanese. Time is just after WW2.
We have good processes
in software development.
Right?
In come the Japanese. Time is just after WW2.
Also, we govern our
projects with proven stuff:
ISO, PMI, …
We know our way
around top technologies:
Java, .Net, JavaScript…
Yet sometimes…
Or most times
Or pretty much
All the time
But there is light…
RUN SMALLER PROJECTS
RUN AGILE PROJECTS
TAKEWAYS FROM “CHAOS REPORT”
CHAPTER TWO – “AGILE TODAY”
“AGILE” IS JUST AN UMBRELLA TERM FOR MANY METHODS
• The term “Agile” was oined in 2001. in Utah as a common denominator
• Defined by a set of principles and the Agile manifesto
STRONG POINTS OF ALL AGILE METHODSoMorale stays high for a long timeoAll methods focus on result, not the by-productoFeedback cycles are fasteroBetter communication is enforcedoTransparency is built-inoTools for implementation are simpleoHigher predictability of end-results (budget, date, scope, quality)
State of Agile 2016.
State of Agile 2016.
AGILE DEFAULTS TO SCRUM
AGILE IS MAINSTREAM
TAKEWAYS FROM “AGILE TODAY”
CHAPTER THREE –“AGILE
SURVIVAL KIT”
“Scrum is a framework for developing and sustaining
complex products.”
FRAMEWORK
(COMPLEX) PRODUCTS
DEVELOPMENT
LET’S PUT THAT IN PERSPECTIVEPROJECT MANAGEMENT APPROACHES
PMI (PMBOK)
IPMA
METHODOLOGICAL LANDSCAPE IN SOFTWARE DEVELOPMENT
SOFTWARE DEVELOPMENT PRACTICES
CONTINUOUS INTEGRATION
CONTINUOUS DELIVERY
TDD
PORTFOLIO MANAGEMENT PRACTICES
LEAN PORTFOLIO MANAGEMENT
PRINCE2
PPM (PMI)
SOFTWARE DEVELOPMENT FRAMEWORKS
LEAN AND KANBAN SOFTWARE DEVELOPMENT
RATIONAL UNIFIED PROCESSING
SCRUM AND OTHER AGILE
WATERFALL
V-SHAPE
…
DON’T GET RID OF YOUR PMO JUST YET!
JUST MAKE IT MORE AGILE
TOP 10 ANTI PATTERNS OF SCRUM USAGE
#1 NOT WILLING TO ADAPT YOUR PROCESS
SCRUM IS NOT A PROCESS. IT’S A FRAMEWORK FOR EMPIRICAL PROCESS CONTROL
IT’S A VEHICLE, NOT THE DESTINATION
#2 MAINTAING THE PRODUCTION
SCRUM IS TIMEBOXED. IT’S YOUR FIRST CLUE
ITERATIONS PROMOTE FOCUS FOR 1-4 WEEKS. CAN YOU WAIT THAT MUCH? USE KANBAN OR WATERFALL FOR THAT.
#3 JUST SHORT OF A TEAMTHERE’S 2 OF YOU. YOU ARE A COUPLE. GET A ROOM.
EVEN AT 3, YOU SHOULD COSINDER ALTERNATIVE GROUPING METHODS
#4 UNABLE TO HAVE STABLE TEAMS
FIRST OF ALL – I AM NOT BUYING THIS. STOP STARTING AND START FINISHING.
OVERBURDERN WILL HAPPEN, THE PRINCIPLES ARE NOT ACCEPTED
#5 PROJECT TOO SIMPLEBACKLOG IS NOT LARGE ENOUGH FOR AT LEAST 3 SPRINTS? REMEMBER: COMPLEX PRODUCTS
NOTHING TO LEARN ALONG THE WAY, JUST REPETITIVE WORK? USE KANBAN OR WATERFALL.
#6 HETEROGENOUS SKILL SETS
1 DEVELOPER, 1 DB GURU AND 1 SCIENTIST WALK WALK INTO A PLANNING POKER GAME.
PULL PRINCIPLE WILL NOT WORK. PARTS OF THE FRAMEWORK ARE STILL USABLE.
#7 DON’T WANT TO LEARN (SCRUM)
SCRUM IS NOT SIMPLE AND WILL NOT BRING RESULTS UNLESS YOU LEARN AND RE-LEARN IT.
COACHING; INTERNAL TRANSITION TEMS; READING A LOT. KEYS TO SUCCESS.
#8 DON’T BELIEVE IN ITORGANISATION WANTS THE BENEFITS, BUT DOESN’T LIKE THE PRINCIPLES.
PRACTICES WILL RARELY WORK WITHOUT ACCEPTING THE PRINCIPLES
#9 SELECTIVE SCRUMSCRUMBUT CITY. YOU ARE PROBABLY RUINING IT.
ARE YOU SURE YOU KNOW WHAT YOU ARE DOING?
#10 DON’T LIKE BIG CHANGESCRUM IS OPINIONATED ABOUT ROLE NAMES.
SCRUM CHANGES A LOT OF THINGS AT ONCE.
top related