Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
Agileee 2011 & Management 3.0Summary from:
Monika Kovachka-Dimitrova
Boris Spasov
Basic information
3rd edition conference
Excellent key note speakers
4 parallel master classes
Conference – 370 people from over 20 countries (including 1 from South Africa)
© 2011 SAP AG. All rights reserved. 2
Africa)
www.agileee.com
Master class Management 3.0 from Jurgen Appelo based on the book
http://www.management30.com/
Impressions and organization
© 2011 SAP AG. All rights reserved. 3
Key notes (1) Alistair Cockburn
Beginners want 1 answer that fits all, Journey man collects practices, Masters create practices because it all depends!
“People are solving a complex problem that keeps changing all the time and they
don’t understand, they are creating a solution that they don’t completely understand because they just started and keeps changing and expressing ideas in language that often is not understand and keep changing.”
Team based design – how teams make better design – rules of nature
1) Craft
© 2011 SAP AG. All rights reserved. 4
1) Craft
2) Cooperative Game
3) Flow management
4) Knowledge acquisition
5) Self-awareness (personalities)
Craft – “Craft teaches us to pay attention to skills” “In craft profession you learn all the time”
1. Shu – Learn 1 technique and just do 1-2-3 step, needs 1 answer only, stop learning
2. Ha – Collect techniques and experiment (Journey man)
3. Ri – Master – invent special blended techniques “It depends”
Key note – Elisabeth Hendrickson (Test Obsessed)
Agile teams: deliver value in frequent release of software at a sustainable pace, while adapting to changing needs of the business.
J.B. quote “Agile practices reduce the accidental complexity in the project.”
Speculation is the lack of alignment of the Intentions to the Implementation to the Actual Need and Risks are the places were this differs. Speculations
© 2011 SAP AG. All rights reserved. 5
the Actual Need and Risks are the places were this differs. Speculations accumulate through the project phases.
There is an ideal level of knowledge (gap).
Learn fast and get empirical evidence.
Continuous Integration is the heartbeat between expectations and implementation.
Letter & Spirit
Day 1 – sessions (Monika)
Vasco Duarte – How agile is your project? – Check list for the beginning, middle
and end of the project to check what are you doing in the project. There is no easy
answer because we see the world from our “cave”.
http://bit.ly/agilesScoreSheet
Francois Bachmann – “Myths, Monsters and Legends” – Myths are told on
© 2011 SAP AG. All rights reserved. 6
Francois Bachmann – “Myths, Monsters and Legends” – Myths are told on
ceremonies their goal is to federate the values and involves superheroes. Legends are the official shape of rumors and their purpose is education. Monsters
impersonates the resistance and require the hero to go beyond it.
Henrik Berglund - Is Scrum incompatible with your brain? Responsibility process
go through Denial, Lay Blame, Justify, Shame, Obligation to Quit or take
Responsibility. (Bad day is when you got stuck, Good day 75% think is when you
made progress and fixed problems) www.christopheravery.com - Leadership gift.
Day 2 – sessions Monika
Petra Scappa – Large Scale Agile Transformation – 4 case studies of large
companies transformation were show. The successful tips: 1) Pilot a group, use
volunteers, have a strong sponsor, take risks (tear down walls); 2) Just do Scrum at large (Larmans’ book); centralized support and coaches that can travel to each
location, local leaders to make sure it happens, visibility, CoPs on different level –
local and global (First 0 bug release); 3) Agile roadmap – holistic approach, Chief Agilest who gathers experts to build plan for development, testing, continuous
© 2011 SAP AG. All rights reserved. 7
Agilest who gathers experts to build plan for development, testing, continuous builds, etc.; 4) It is not just for the stamp, because it is fancy.
Timofey Yevgrashyn – Musketeers game – Card game for taking out the
problems and finding solutions – good for retrospectives.
Max Griponov - Paper prototyping – stencils and printouts, transparent films –
you can think, create, change and test. Testing with Facilitator and Watchman.
Key note – J.B.Rainsberger
Will try – the saddest words of a developer
When we describe something the human brain looks for:
1) To find similarities;
2) Abstract them out & look to describe the differences
The LEMON example
© 2011 SAP AG. All rights reserved. 8
The LEMON example
Getting things done – David Alan – enough for test list:
1) Free your mind for great work
2) Estimating work for making a flow and short cycles (how do we eat an
elephant?)
3) How quickly we actually go
Bill Caputo – “XP is in here (heart), not out there” XP is what you do when you master the basics, and you have discipline and the attitude, approach and philosophy.
Day 1 – sessions (Bobi)
Talk “Challenging requirements”
http://agileee.org/2011/05/31/talk-challenging-requirements/
Key message focus on real customer requirements.
Cut scope; Challenge requirements; Refuse solutions to unknown problems.
© 2011 SAP AG. All rights reserved. 9
Refuse suggestions to use technology – you know it better ☺
Don’t rush to solve the first problem they give you.
Start with very high level example of how people will use the system.
Great products come from understanding the real problem and who’s problem is
Facilitation technique – 4 questions while drawing a mind map
What is the desired business change?Who are the people that can create desired effects?
What does the target group want, need, should do?
How should the product or operation be designed to fulfill that?
© 2011 SAP AG. All rights reserved. 10
Day 1 – sessions (Bobi)
Multiple speakers (en)lightening talks
If things in the team are not running - perform retrospective only on positive achievements.
Accidental cost > 10 than normal – no craftsmanship, no techniques – TDD ->
scrum without XP can not work.
© 2011 SAP AG. All rights reserved. 11
scrum without XP can not work.
Barry O’Reilly I don’t do agile, I am agile – ask your self why are we doing it.
Day 1 – sessions (Bobi)
Andrea Provagilo
Overcoming self organization blocks
© 2011 SAP AG. All rights reserved. 12
Overcoming self organization blocks
Software is intangible and complex and we need to collaborate
Why do we do agile - > software dev is empirical -> feedback loops
Teams are systems – people sitting in the room – anthropological system
We come form waterfall -> result of industry -> education system is not designed to collaborate -> to support industry
We need to evolve -> self-organization
Organizations - structure
You are accountable and report to.
There are interactions between levels
Levels of influence – seniority, tech competence
© 2011 SAP AG. All rights reserved. 13
Day 2 – sessions (Bobi)
Danny Kovatch
Motivation 3.0 and Agile
http://agileee.org/2011/05/31/talk-motivation-3-0/
Reward improves routine work but it kills creativity.
© 2011 SAP AG. All rights reserved. 14
Management: Consider workers are volunteers
If you want to motivate someone -> mastery, purpose + let the folks do the work
Lasse Koskela Agile and versioning control – source versioning should support the
goal not vice versa
Alexey Krivitsky Offshore In Ukraine – primitive but with big potential
Antonio Terreno Programming anarchy – extreme case of development and customers collaboration. Start up incubator.
Key note – Juergen Appelo(How to change the world?)
Change of Complex Adaptive System
1) Consider the system
1) PDCA cycle - Plan (What is your goal? Where it is going well?); Do (What are the
crucial steps? When and where do you start?); Check (How do you get feedback? How
do you measure results?); Act (How do you accelerate Results?)
2) Good KPIs – 1) Relative to stakeholder purpose; 2) Helps to improve an aspect of the
system; 3) Part of the work of those who are interested in it (NOT bound to Incentives)
© 2011 SAP AG. All rights reserved. 15
system; 3) Part of the work of those who are interested in it (NOT bound to Incentives)
3) Agile managers are friendly monsters
2) Consider individuals
1) ADKAR model – AWARENESS, DESIRE, KNOWLEDGE, ABILITY & REINFORCEMENT all the time
3) Consider the interactions
1) Adoption Curve model
4) Consider the environment
1) 5 I’s model – Information, Identity, Incentives, Infrastructure, Institutions
Management 3.0 Teaser
© 2011 SAP AG. All rights reserved. 16
Thank You!