There are a number of reasons why agile is under attack. In this article, the author looks at the role of management, the confusion over the meaning of “agile,” and the fact that agile is not always the best fit. Learn what you can do to resist the “attack”!
You searched for: ∨derBy=RANK∨derBy=RANK (∨DERBY=RANK∨DERBY=RANK)
20204 items found
Psychological safety—the belief that one can communicate ideas, questions, concerns or mistakes without negative consequences—is one of the most important factors in team productivity and morale. Here are 16 ways to foster a project environment where people feel free to share their ideas, perspectives and feedback.
How do we incorporate the business world’s increasing reliance on specialists into organizations with stable, cross-functional agile teams? The concept of components teams is a good solution, but in some cases a consultant model will be a more effective approach.
There can be significant value in planning, but it is possible to plan too much. Determining the right level should be based on a collection of factors such as the complexity and risk of the situation, the skills and experience of the people involved, and the uncertainty that you face.
With more businesses having both predictive and iterative projects on the go, PMOs need to flex their core functions to support agile ways of working. Here are three areas for PMOs to focus on when supporting multiple delivery methods.
To further assist in the health check process, this series continues with an examination of the rationale as to why each statement within each dimension is deemed to represent a healthy practice. In this installment, we look at the statements in Section 4 of the PMO Health Check Worksheet: Post-Project Deployment Performance Monitoring and Incentives Management.
Reduce your overall effort—and keep a trained and productive team in place—by using informational resources provided by your PMO. Your PMO provides guidance and templates that will be useful throughout your project to keep your team prepared and productive.
This session will walk the attendee through 10 practices that are sure to be problematic. Topics will include but are not limited to: 1. Including summary tasks in project sequencing; 2. Assigning resources to summary tasks; 3. Constraining activities rather than sequencing dynamically; 4. Scheduling project tasks as late as possible; 5. Leveling resources without analysis; 6. Inadequate baselining techniques; 7. Using elapsed durations for team schedules; 8. Incorrect calendar association resulting in incorrect schedules; 9. Organizing project tasks incorrectly forcing incorrect reports. 10. Dismissing Agile Tools Objectives: After attending this session the attendee should be able to: 1) identify inappropriate practices in their MS Project schedules. 2) Resolve issues created by these practices and 3) leverage their learning in future project plans by avoiding the recurrence of inappropriate practices.
In your day-to-day practice of project management, questions often arise and you need to find the answers. PMI has been publishing articles to help you find solutions since the profession was founded; there are over 9000 articles in the Learning Library alone. Let us help you understand the different types of content available and how to access them, how we have recently improved the PMI.org search function and how to make your own contribution to this valuable collection and share your expertise with other practitioners.