Agile Project Management

The purpose of the Agile Project Management track is to help people learn the skills, techniques and mindset needed to orchestrate a team effort, collaborate with stakeholders, and adjust the team's work for maximum effect.

We are careful in this track to separate the skills of project management from the job title "Project Manager". In many settings using agile development, there is no one with that title, possibly the entire team is self-organizing or self-managing.

Even in self-organizing or self-managing teams, however, it is beneficial for one or more people on the team to have skills in helping the team work more cohesively, communicate more effectively with their stakeholders, and reflect and adjust on their working habits.

This track is currently under development. The following shows the current state of the discussion. We will post more as specific topic areas and learning object clusters solidify.

1.1. : Soliciting feedforward and feedback.
1.2. : Risks and possible risk mitigation.
1.3. : Priorities and dependencies.
1.4. : Planning, replanning, prioritizing, reprioritizing.
1.5. : Incremental development and deployment.
1.6. : Using increments as well as iterations.
1.7. : Attending to internal quality as well as external.
2.1. : Identifying and engaging stakeholders.
2.2. : Shared understanding of success, expectations.
2.3. : Communicating shifts in progress and outcomes.
2.4. : Maintaining stakeholder relationships.
3.1. : Ensuring adequate skills coverage in all areas.
3.2. : Helping form cross-functional teams.
3.3. : Creating a safe team environment .
3.4. : Establish collaborative habits.
3.5. : Reflect and improve.
3.6. : Align project and team goals and priorities.
4.1. : Choosing planning method to suit project characteristics.
4.2. : Estimating and planning collaboratively.
4.3. : Planning & committing at multiple granularities.
4.4. : Adjusting estimates and plans during the project.
4.5. : Including full organizational needs in plans.
4.6. : Understand, capture and use velocity.
4.7. : Under- versus over-committing.
5.1. : Creating a safe environment for bad news to surface.
5.2. : Helping the team surface risks, worries, and bad news.
5.3. : Communicate risks.
5.4. : Help remove problems.
5.5. : Monitor the team's ability to detect & resolve problems.
6.1. Helping the team reflect and improve on their working habits.
6.2. Helping individuals improve their own effectiveness.
6.3. Adjust team composition.
6.4. Challenging wasteful process elements.
6.5. Share ideas with other teams for organizational improvement.
6.6. Help introduce new ideas and techniques.

Contact us

International Consortium of Agile (ICAgile)
1000 Peachtree Industrial Blvd, #6434
Suwanee, GA, 30024

Stay in touch