Continuing to develop a failing project is a big challenge. Improving the environment and culture to ensure successful delivery requires integrating the bottom-up approach from a small task level with a top-down orientation of strategic management. Learn how to diagnose failure and implement useful techniques.
Extreme projects feature high speed, high change, high complexity and high stress. As more projects continue to fall into the extreme zone, successful project and program managers will shift from inhibiting change to proactively creating change and responding to change.
What happens to a PM who is trying to adopt Agile? Dave Prior, PMP discusses the struggles you can expect to encounter while showing you how creating a Personal Agility Canvas tool can help make things a little easier.
Learn From Others
The best agile software teams communicate well, push hard to meet deadlines, support each other when struggling with issues, and go above and beyond to maintain quality. The key element is trustworthiness. In this article, the writer provides a self-assessment tool that will allow you and your team members to assess and demonstrate trustworthiness over time.
|A.||Agile does provide a way to use non-functional requirements in its methodology, but often it is overlooked or not stressed when new teams are preparing their first few projects. Make a point to add them into your new process.|
|B.||The reason agile projects are completed so much faster and provide so much more value is that with the Scrum practice methodology, it is no longer necessary to consider vague things like non-functional requirements. If they aren’t going to function anyway, why bother with them.|
|C.||User stories are only written if there is a need for outside personas to be created to represent users. Non-functional requirements are the ones assigned to those personas who would not be interested in your product or service, and therefore can be excluded from consideration.|
|D.||Many projects have both functional and non-functional requirements that impact the outcome of the project. That is why only traditional processes should be used. Agile processes work only on software projects, and then only when there is an absence of non-functional requirements to be considered.|
Trying to implement agile DevOps in a traditional DevOps environment is a huge challenge without first changing underlying governance practices. In this article, the author explains why--and identifies some success factors.
If you’re the project manager for a geographically distributed team, you have likely encountered time zone challenges in running your meetings. Here are some alternatives to consider.
As more and more organizations recognize they need both agile and waterfall project execution processes in order to succeed, teams are being asked to work in very different ways.
How do the biases, effects, fallacies, illusions and neglects outlined in Kahneman’s Thinking, Fast and Slow (2013) affect decision making? By applying Kahneman to the Knowledge Areas of the PMBOK® Guide, the author illustrates how project managers can mitigate the effects of irrational thinking.
Are command-and-control undertones hurting your organization's performance? Are people getting the passion and desire to contribute slowly crushed out of them by project management bureaucracy and prescriptive process? Then free them to be hyper-productive by emphasizing collaboration.
Some topics in agile testing may point to dysfunctional organizational practices that are often taboo, off limits or avoided in regular conversations. In this article, we identify four such topics that need to be discussed and addressed for agile success.
One of the cornerstones of agile is the concept of self-managed teams. Does that concept translate into more traditional project areas?
Companies seeking to cope with the pace of accelerating change are looking for ways to go faster, and managers in non-technical disciplines have become increasingly infatuated with the agile software development methodology. Agility sounds like a good thing, and agile marketing sounds like it must be better than regular marketing...but is it?
Ask a Question