Provocative thinking from the field.
Wouldn't it be better if scheduling tools focused on deliverables rather than the work — the activities and tasks — needed to deliver them? Execution is about creating value, and stakeholders care little about the busy details. Project managers who get this distinction right will reap the benefits of more realistic and achievable plans.
Most large organizations have established project, program or portfolio management offices, but there is a disconnect between many PMOs and the wider businesses they support, according to a group of senior executives and academics that studied the trend. They recommend that some organizations would be better served by a decentralized approach that creates “pseudo PMOs.”
The best process for your project should be determined by careful consideration of key factors, including overall complexity, the level of risk involved, and time-to-market requirements. Often, a flexible hybrid approach fits best, but it must agreed upon by management and the team before the project starts.
Programming and testing are two completely different skills. When it comes to validating that requirements have been met and new issues haven’t been created, programmers need to step away from their own work; testers need to think like users and treat the system like a mystery.
So much hinges on the project schedule, yet so few team members contribute to it. Whatsmore, they typically don’t care about critical paths, constraints and other building blocks; they just want to know “what, where and when.” We're overdue for consensus-based planning tools that bridge execution and analytics.
The problem-solving skills on which project managers largely build their reputations might be greatly improved by mastering the challenge of problem-selecting instead. In short, the difficulty isn’t the problem; it's how we’re coping with it. Radical acceptance is a start.
Most large global organizations will rely on “activist” enterprise program management office (EPMO) leaders by 2017, according to research analyst Gartner. The emerging role is a response to the need to significantly improve strategic execution, and increased pressure toward innovation and differentiation.
Yes, project success or failure is ultimately the responsibility of you, the project manager. You’re in charge of everything, from planning and reporting to monitoring risk, budget and schedule. But there are other people who must take ownership of their parts of the project. And it’s also your job to make that clear.
Project managers and business analysts share many challenges and concerns, particularly in the areas of requirements, communication, stakeholders and professional development. Here are seven emerging trends, ranging from smaller projects to fewer emails, that BAs and PMs should be tracking and leveraging in 2014.
Organizations are releasing software as soon as possible, skimping on Quality Assurance, squeezing testers, and pointing fingers when it all goes wrong. As our series concludes, we look at the final two reasons that they should just do away with software QA completely (but not really).