The Project Manager and Modern Agile Projects

Slides:



Advertisements
Similar presentations
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Advertisements

AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Agile 101.
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
Does it work with Data Warehouses?. “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we.
Introduction to Agile.
Agile Project Management By: Jim Highsmith Presented by: Brian Faulk.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
BEFORE AGILE METHODS Other Engineering fields development models were used, ie: Waterfall Method: Intensive planning and refactoring before coding is actually.
Software Development Landscape
Agile Programming Principles.
The Agile Primer July 2008 © ThoughtWorks 2008.
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
9/12/20151 Copyright© 2007 The Oobeya Group, LLC.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
What Is an Agile Leader? Todd Little Sr. Development Manager.
Copyright © 2010 Ivar Jacobson International SA. All rights reserved The changing face of Project Management What “Agile” brings to the Project Manager.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
Lecture 3 – Agile Approach
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
10 key principles of agile software development
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
JASS 2006 Agile Software Development. JASS 2006 Agenda.
©Alistair Cockburn The 2005 “Declaration of InterDependence” Alistair Cockburn
Alistair Cockburn©Humans and Technology, Inc., Slide 1 The Role of the Manager in Modern Agile Projects Alistair Cockburn Humans and Technology.
Slide 1 ©Alistair Cockburn 2009 Project Management as Pharma: Sometimes the opposite of a good strategy is a better strategy Dr. Alistair Cockburn Humans.
Agile Gintarė Bernotaitytė © 2013.
Alistair Cockburn©Humans and Technology, Inc., Slide 1 The Current Conversation in Agile Software Development April-2004
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Project Workflow.
Agile development: a PM’s perspective
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Methods SENG 301.
Shifting to Agile: Are University Libraries Ready?
Flight Software Conference 2016
The Agile/Non-Agile Debate
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
7 Sins of Scrum and other Agile Anti-Patterns
Waterfall, Agile & Scaling Agile
Project Workflow.
 Crystal methods are part of the Crystal family developed by Alistair Cockburn in the mid- 1990s  Based on observations of many teams that did not follow.
X4MIS Change Management Principles
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Case Studies Motivating Efficiency as a Spendable Quantity
Agile Software Development The Cooperative Game
Navigating an Agile Transformation
Client Management Managing Client Expectations
Crystal (How to make a methodology fit)
Taking an Iteration Down to Code
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
7 Sins of Scaling and other Agile Anti-Patterns
How to Successfully Implement an Agile Project
Teaching slides Chapter 11.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Chapter 3 – Agile Software Development
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Projects, Assignments, and other Assessments
Agile software development
Adapting Agile in Pharmaceutical Industries
Chapter 5: New and Emerging Process Methodologies
System Development Methods
Engaging Senior Executives
Presentation transcript:

The Project Manager and Modern Agile Projects Alistair Cockburn Humans and Technology http://Alistair.Cockburn.us

Often things don’t go as planned Often things don’t go as planned. Sometimes the original plan is the WRONG one! How do you know which is right? How do you know where you are? What do you do at the moment of crisis? planned route to planned goal route to planned goal (1969 lunar landing) Moment of crisis! Another way of look at adaptation is by looking at your approach to the project. You can plan to go directly from point A to point B (the red dashed line). But this in reality never happens exactly as planned, so instead you use various project management mechanisms to ensure that you reach Point B (the green connected line). With an adaptive process, you might not end up at Point B and that’s a good thing. Your customer has, through the experience of the project and collaborating with developers, realized that Point C is actually a better place to be. Without adaptation, there is a tendency to force something on the customer, even if it is clear that they really need something else. route to better goal (“Titanic” movie) getting lost route to worse goal (ship Wasa)

The 2005 “Declaration of Inter-Dependence” for agile-adaptive project-product managment 10 project Critical Success Factors and the role of the PM in even rabidly agile projects How to find useful PM strategy ‘nuggets’ right under your nose Using agile strategies in everyday situations

AgileManifesto.org (2001) Individuals and interactions over Processes and Tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan “... while there is value in the items on the right, we value the items on the left more.”

pmDeclarationOfInterDependence.org (2005) We -- increase return on investment by making continuous flow of value our focus. deliver reliable results by engaging customers in frequent interactions and shared ownership. expect uncertainty and manage for it through iterations, anticipation and adaptation. unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference. boost performance through group accountability for results and shared responsibility for team effectiveness. improve effectiveness and reliability through situationally specific strategies, processes and practices."

The 2005 “Declaration of Inter-Dependence” for agile-adaptive project-product managment 10 project Critical Success Factors and the role of the PM in even rabidly agile projects How to find useful PM strategy ‘nuggets’ right under your nose Using agile strategies in everyday situations

Historically, “agile” is low-ceremony, light process and people-communication-intensive “When you want your boat to go fast, it is easier to cut anchors than add horsepower.” -- Luke Hohmann Common Practices Delivery working product often Colocate team members Write schedule in bits of paper hung on the wall Lighten or dump the heavy requirements document, heavy project plan, long status mtgs Decentralized Control (Revenge of the laborers) “We don’t need no stinkin’ project managers tellin’ us what to do !” (in actuality, Reallocation of Control)

Always, the players in the game are PEOPLE - and People are stuffed full of personality Methodology Ecosystem Values Values Activities Milestones Jenny Jim Peter Annika Quality Process Teams Tester Designer Documenter Project manager Products Techniques Roles People Standards Tools Skills Personality

10 Critical Project Factors. Nourishment from Executive Sponsors (decisions, money) Community (communication, amicability) Focus (known priorities, focus time) Incremental development & Reflection People (abilities, motivation)

Amicability & Goal alignment Amicability : Willingness to listen with good will Low “amicability index” means people block the flow of information, intentionally or through not listening well. “Amicability index” indicates how easily information passes from one part of the organization to another. Goal alignment Normal team Aligned team

(communication, amicability) (known priorities, focus time) Role of the Project Manager on modern projects: Pull in support, motivate team, block interrupts. Sponsor(s) Interruptions Decisions $ Visibility X PM Community (communication, amicability) Focus (known priorities, focus time) Nourishment from Executive Sponsors (decisions, money) People (abilities, motivation) Incremental development & Reflection Communication Amicability Priorities Focus time Skills development Motivation Reflection developers

The Project Manager’s timeline Executing & Steering (& more Planning) Initiating Planning Closing Initiating Mission statement (1-2 pages) Project priorities chart Planning Project map (low-resolution PERT chart, no times) Blitz planning technique Allocation of people & times to project map (schedule) Executing & Steering Strategies to avoid & get out of trouble Strong-visibility status charts (information radiators) Pause, reflect, change (both process & plan!) Closing - (retrospectives)

The 2005 “Declaration of Inter-Dependence” for agile-adaptive project-product managment 10 project Critical Success Factors and the role of the PM in even rabidly agile projects How to find useful PM strategy ‘nuggets’ right under your nose Using agile strategies in everyday situations

Create your own ‘nuggets’ by introspection into “short war stories with happy endings” 1. Identify a time when things got ‘better’. 2. Examine the story in slow motion and identify the turning point. 3. Locate the principle. 4. Find 2 more projects with the same principle and same type of positive shift. 5. Truth-in-advertising: Name the side effects and overdose effect.

Project management requires Detecting and creatively (avoiding) (getting out of) messes. Osmotic Communication Expert in Earshot Cone of Silence Early Victory Early and Regular Delivery Walking Skeleton Incremental Rearchitecture Sacrifice One Person QA-Rotation SWAT-fix team Cross-specialized Team Function / Component Owners Pause, Reflect, Change Timeout/Regroup Part-Timers as Advisors Process Miniature Progress & Training Teams Rejoining Streams Short-horizon planning Spare Leader Capacity Spike Gold Rush Project 360° Safe Solutioning Session

Write your ‘nuggets’ as ‘prescriptive medication’: PRODUCTIVITY: Gold Rush You can’t wait for requirements to settle, so... Action: Start design and programming immediately; adjust requirements weekly. Requires: Good communications Side effect: Manage communications, plan for rework! Overdose: Rework holds up the project Example: Concurrent development (Winifred)

TEAM BUILDING: Walking Skeleton Action: Connect the architecture together with simple “hello, world” function as 1st running code. Build up both infrastructure & function from there. Benefits: Early Victory, executing architecture, Allows parallel development Side effect: Must manage rework of infrastructure during function development Overdose: Too simplistic: over-rework of infrastructure delays project Examples: NBO project

TEAM BUILDING: Early Victory Action: Ensure the team delivers something as early as possible, even if only a Walking Skeleton. Benefits: Team learns each other, process Sponsor sees team working together Side effect: Must manage expecations for early delivery Overdose: Too simple = Not enough process exercised, not real confidence built Examples: Walking Skeleton

The 2005 “Declaration of Inter-Dependence” for agile-adaptive project-product managment 10 project Critical Success Factors and the role of the PM in even rabidly agile projects How to find useful PM strategy ‘nuggets’ right under your nose Using agile strategies in everyday situations

Agile techniques on non-sw projects Kids’ Homework: Walking Skeleton, Increments, Continuous integration Book Publishing: Colocation, Concurrent development Building a basement under our house: Daily stand-up, Revise the plan, Plan/Don’t plan ahead Packing the House under Deadline: Incremental by room, Burn-down chart

(communication, amicability) (known priorities, focus time) Role of the Project Manager on modern projects: Pull in support, motivate team, block interrupts. Sponsor(s) Visibility Decisions $ Interruptions X PM developers Communication Amicability Priorities Focus time Skills development Motivation Reflection Community (communication, amicability) Focus (known priorities, focus time) Nourishment from Executive Sponsors (decisions, money) People (abilities, motivation) Incremental development & Reflection http://Alistair.Cockburn.us