Agile Project Management By: Jim Highsmith Presented by: Brian Faulk

Agile Project Management By: Jim Highsmith Presented by: Brian Faulk

APM Brief – Description: A style of product development that concentrates on adaptive and exploratory, rather than anticipatory and prescriptive management.

Reliable Innovation There are five key business objectives for a good exploration process such as Agile Project Management (APM) 1. 2. 3. 4. 5. Continuous Innovation- To deliver on current customer requirements. Product adaptability- To deliver on future customer requirements. Reduced delivery schedules- To meet market windows and improve returns on investments (ROI) People and Process Adaptability- To respond rapidly to product and business change. Reliable Results- To support business growth and profitability

Reduced Delivery Schedules The iterative, feature-based nature of APM contributes to reducing delivery schedules in three key ways: focus, streamlining, and skill development.

Reduced Delivery Schedules Cont. Focus – First, the constant attention to product features and their prioritization in short, iterative time boxes forces teams (customers and developers) to carefully consider both the number of features to include in the product and the depth of those features. Constant attention reduces the overall workload by eliminating marginally beneficial features.

Reduced Delivery Schedules Cont. Streamlining – APM—like its lean development counterparts— streamlines the development process, concentrating on value-adding activities and eliminating overhead and compliance activities. Skill – Development APM focuses on selecting and developing individuals with the right skills for the project.

Core Agile Values Agility is more attitude than process, more environment than methodology. In 1994 authors Jim Collins and Jerry Porras (1994) wrote Built to Last, a book based on their research that set out to answer the question, "What makes the truly exceptional companies different from the other companies?"

Core Agile Values Cont. The Manifesto for Agile Software Development established a set of four core values, which with a single word change, form the core values of APM – “We are uncovering better ways of developing [products] by doing it and helping others do it. Through this work we have come to value:” – Individuals and interactions over processes and tools Working [products]5 over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan. “That is, while there is value in the items on the right, we value the items on the left more.” While these core value statements were originally written for agile software development, they apply directly-with a bit of interpretation, and some reordering –to APM.

Agile Project Management The central question for project managers, project team members, and executives is, "How does project management add value to a project?" Unfortunately, many development engineers consider project management to be a roadblock—a hindrance, not a help. – Project managers are viewed as administrators who put together detailed task schedules, create colorful resource profiles, bug team members about micro-task completions, and write reams of status reports for upper management, not as direct contributors to delivering value to customers. APM is a set of values, principles, and practices that assist project teams in coming to grips with this challenging environment. The core values of APM address both the need to build agile, adaptable products and the need to create agile, adaptable development teams.

The APM Framework One of the most common questions about APM is, "What about the planning, architecture, and requirements phases?" The simple answer is that these things are activities and not phases. An agile approach can easily include as much time for these activities as in a conventional serial phase approach, but the activities are spread across multiple iterations. A second area of concern is the risk of rework in agile development if the initial architecture work (the discussion in this section could refer to architecture, plans, or requirements) misses a critical item. Within this general APM framework, the successful completion of each phase depends upon a series of key practices that actually guide the work effort. Values and guiding principles describe the why of APM, and practices describe the how.

Our Journey APM isn't for everyone or every project; it is not a universal best practice. APM works well for certain problem types, in certain types of organizations, with people who have a particular cultural perspective, and for managers who have a certain worldview APM is not defined by a small set of practices and techniques. It defines a strategic capability to create and respond to change, to balance flexibility and structure, to draw creativity and innovation out of a development team, and to lead organizations through turbulence and uncertainty.