How do we achieve more with less? Why Agile / HaMIS story Prerequisites SCRUM Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 1
Achievements Improving “Funtionality” Architecture delivered within Every 3 weeks we constraints time ship software in and € production Happy users 5 stars TÜVIT Developers like Satisfied Business, stakeholders environment and Architect & project challenges manager can get along :-) Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 2
HaMIS, Port of Rotterdam, Harbour master Management Information System. 24/7 application for traffic management, transport, environmental safety and crisis management. Goals: 1. Replace outdated system 2. Support the port of Rotterdam expansion Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 3
HaMIS, Port of Rotterdam, Harbour master Management Information System. SG FAB TAB Programma Product Mgr. IVH Owners HaMIS Project Manager HaMIS Productmanagement Teams stakeholder management Stakeholder Stakeholder Operations Externe interfaces Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 4
Where do we come from? Project Start Q&A Architecture 100+ department identified use cases Architecture with 4 layers & 6 subsystems BPEL process server 6 architects 800+ architectural RUP and Scrum but decisions Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 5
Resulting in... One use case in 6 months! Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 6
The assumption is... In advance the Customer knows what he wants! Developer knows how to build it! And nothing will change ! Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 7
Our Solution, Agile Manifesto Individuals and Process and tools ! over ! interactions ! Comprehensive Working software ! over ! documentation ! Customer Contract negotiation ! over ! collaboration ! Responding to change ! Following a plan ! over ! Source: www.agilemanifesto.org ! Edwin de Werk & Viktor Grgi ć dinsdag 29 mei 12 8
The most important for success Hire coaching Work the system. Team Right people, no sheldons Grow a pair and try, learn, try ....... Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 9
The most important for success Trust Fun Shared Responsibility Edwin de Werk & Viktor Grgi ć dinsdag 29 mei 12 10
Team Trust before decision making What am I proud of? Diner after sprint Workshops in hotel ski trips in France Edwin de Werk & Viktor Grgi ć dinsdag 29 mei 12 11
Quality / Architecture extremely important Just-in-time Knowledge Open space sharing just-enough sessions Documentation is Wiki filled by “harvesting” the knowledge Standardization is discovered and not predefined Continuous refactoring towards Architecture principles: better design Simplicity and design for change Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 12
Optimize the whole Hyperproductive Agile team Hyperproductive Agile team jdhjksh Department 2 Department 3 Hyperproductive Agile team Requirements Marketing Architecture gathering Department 4 ...has a challenge Planning Lead User / Department 5 Agile team time Business Analysis Department 6 Department 8 Department 7 Development Delivering Testing Pull , continuous flow, customer value, eliminate waste, continuous improvement Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 13
Product vision, creativity, commitment Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 14
Team members and user No translation between the customer and developer mindset! Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 15
“Everybody, altogether, early on” James O. Coplien 16 dinsdag 29 mei 12 16
Challenges Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 17
Work the system Develop, protect and direct with constraints Intrinsic motivation Make surroundings Scrum friendly Change advisory board vs. sprint release Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 18
Beyond Scrum We don’t ask anymore “What does Jeff say?” Agile / Scrum is part of DNA, we just do it! Stories are more and more defined by teams Real production instead of production ready Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 19
Behaviour & Titles I am an - architect - manager - designer - analyst - scrum master ... “Bureaucracy is here to compensate incompetence and lack of discipline” Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 20
Retrospectives Games can become a goal Not going “deep” enough Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 21
Team or “virtual” team Backlog grooming Which questions are solved by one of the teams and which together Division of stories Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 22
How did we achieve more with less? Less... More... Control Concrete goals Whish lists Vision Procedures and processes Face-to-face customer collaboration Architects, analists, testers, team leads, project Team responsibility and decision managers,... in traditional sense making Technology push, (off-the-shelf) Continuous improvement products and tools with no Trust direct value Demand pull Generic and just-in-case Feedback loops solutions Solutions for harbor master instead Beforehand documentation of “future-proof” and “flexible Extensive use-case descriptions statements” Chickens! Pigs! Edwin de Werk: @eworx4me en Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 23
Meer weten? Edwin de Werk: @eworx4me Viktor Grgi ć : @vgrgic dinsdag 29 mei 12 24
Recommend
More recommend
