Académique Documents
Professionnel Documents
Culture Documents
02
This paper explores two important phases in the transition to Agile project management:
1. Providing a context in which Agile projects can co-exist with traditional projects, under the auspices of a centralized PMO, and simultaneously add value. 2. Leveraging Agile practices to improve the PMOs effectiveness across all projects.
www.thoughtworks.com/mingle
03
Among the many responsibilities of a PMO, four have the greatest impact on Agile project teams:
1. Administering common project reporting for all stakeholders and supporting project, IT, and corporate governance. 2. Providing knowledge transfer in the forms of training, mentoring, and best practices to IT project teams (frequently termed a Center of Excellence). 3. Defining and instituting standards for project management and development processes. 4. Facilitating team collaboration via common metrics, processes, deliverables, shared resources, etc.
Agile projects must participate within the PMO infrastructure, especially when they constitute only a small percentage of the project portfolio. This requires willingness on the part of Agile team management to conform to (at least externally) traditional management practices. But not only must the Agile project adapt: the PMO must as well. It will benefit from Agile projects ability to accurately measure the status of a project and adapt to changing requirements.
www.thoughtworks.com/mingle
04
Certain PMO deliverables, such as detailed documentation on regulatory requirements, may be non-negotiable even if they seem excessive or contrary to Agile project-level principles. The greatest disconnect between Agile and traditional projects stems from Agile teams seemingly incongruent project metrics. Within an Agile project, teams report on velocity (rate at which teams deliver business value), burn charts (trends in remaining effort or task completion), test coverage, and running tested features (features delivered to the business). These are excellent measures of the teams progress towards high quality delivery, and align with the business need to respond to global competition (see Figure 1). But business still demands time, budget, and risk analysis information. It is not difficult for Agile teams to identify and bridge this reporting gap. Then, over time, project teams can work with the PMO to transform management practices to become more responsive to change.
www.thoughtworks.com/mingle
05
www.thoughtworks.com/mingle
06
Along with transforming metrics into PMO standards, Agile teams must comply with other legacy requirementswithout disrupting the day-to-day activities of team members. In a large U.S. investment bank, the PMO required specific metrics measured against budgets and dates, as well as comprehensive documentation to satisfy the companys regulatory compliance. Agile teams met the metrics requirement by managing a story card wall, updated after each daily meeting. Team leaders computed team status from velocity and burndown charts, and reported against PMOs high level milestones. The manager recognized the overhead required to create the compliance documents and took steps to insulate the team by staffing additional resources for this task. Legacy integration also forces some transformation. Agile teams building new capabilitiesregardless of their processes and metricsare often required to follow parts of the legacy SDLC or use standardized tools. For example, in a Top 10 U.S. retail bank, all eCommerce projects contain large mainframe components. The banks standards and policies required the use of a standard defect tracking system and a single generated report containing all severity one issues in production and development for every project. In a medical systems company, all teams were required by auditors to use a standard requirements management tool to provide traceability of delivered capability. In this case, Agile project managers adeptly built in links from the teams lightweight story tracking tool to the legacy toolset, so the team wasnt burdened by the additional overhead.
www.thoughtworks.com/mingle
07
www.thoughtworks.com/mingle
08
In addition to metrics, Agile teams have the ability to impact the PMOs process standards. Companies establish and fund PMOs to administer accepted business management and governance requirements. Agile projects may provide the catalyst for the PMO to reflect upon its existing functions and determine which should be kept, changed, or retired. In one banking organization, for example, input from Agile projects led the PMO to identify unnecessary and redundant documentation requirements (in this case, those that were not tied to regulatory requirements) and cut that which was not necessary. Other organizations have enhanced their testing tools to create documentation from automated tests and thus satisfy existing requirements in a new way. Yet other PMOs have instituted architecture-independent processes based on Scrum practices. In adopting these types of changes, the PMO becomes the vehicle to communicate not only best practices, but also templates and specific examples from past projects.
Enable Collaboration
There is a direct correlation between the degree of collaboration on a team and the teams ability to achieve agility. Collaboration among team members is critical to both problem definition and resolution, particularly for teams addressing frequent changes in short delivery cycles. It is essential that project managers focus on effective interpersonal communication and foster collaboration for developers, testers, business stakeholders, and other team participants.
An Agile Approach to Project Management Leveraging Agile Technology plays Practices to type of team culture. For co-located teams, the a key role in supporting this Improve collaboration solution may be a mix of physical artifacts (e.g., post-its on a white board) and PMO Effectiveness technology (e.g., team wiki for persistent discussions). But as companies form distributed teams,
the requirements for technology-based solutions increase. Teams need real-time collaboration (e.g., instant messaging, videoconferencing), flexible programming environments (e.g., distributed Liz Barnett SCM and build management), and visibility into all project artifacts and metrics (e.g., shared EZ Insight, As repository and dashboard). Inc. companies emphasize collaboration, they also need to de-emphasize non-critical tasks. Data must be collected seamlessly, without impeding the teams productivity or disrupting communication. Developers should not have to halt their daily activities Juky 2008 to enter status data into secondary tools. This is an issue that has plagued development teams for decades; the advent of short iterations makes non-intrusive metrics collection even more critical. Collaboration is not unique to Agile development, but Agile teams bring these requirements to the forefront. They are staffed with heterogeneous skills, have inflexible timeframes, and, like any other team, require access for IT and business management to projects issues and risks. Their emphasis on collaboration should pave the way for non-Agile projects to also improve productivity and quality.
09
www.thoughtworks.com/mingle