Best practices, lessons learned and advice from your peers in the trenches.
How they affect the project can vary from company to company, project manager to project manager and project to project, but each of these seven factors — spanning budgets and resources to stakeholders and requirements — will have severe negative implications for the success of any project.
An Agile approach to budgeting recognizes the need for frequent course correction by outcome owners who can respond to the business when they have autonomy. It favors accountability over expenditure tracking; it's using road intersections with roundabouts (cooperation) rather than traffic lights (compliance).
Team innovation can be greatly influenced by conflict (either productive or destructive), experiential diversity, a sense of empowerment, and organizational boundaries. An Agile approach can help, though there are pros and cons to consider. Spotify offers a real-world example of how it works.
Successful resource management starts with instilling processes that balance workloads and match skillsets. It also requires the ability to adapt to shifting demands and priorities. And it’s all tied together by communication of real-time data. How well is your organization implementing these principles?
Estimates are far from perfect, but the business side is always going to want some sense of “how long, how much?” — even on Agile projects. Technical teams may have the most relevant knowledge to answer, but they don’t always have the willingness or tools. Here, Rex Madden of Stride NYC frames the issue and discusses options. [30 min.]
Problems emerge when a company tries to create products for external customers using processes meant for internal technology development. Here’s an explanation of the vast differences between the IT and product organization models, from mindset to metrics.
Like the telephone game in which a message changes as it is whispered from one person to another, a lot can get lost as strategic initiatives travel across an organization, from idea to plan to execution. But it’s no secret that transparency is key to keeping priorities aligned.
Value-driven projects differ from plan-driven projects in significant ways, including how teams are formed, how funding is obtained, how scope is determined and how solutions are achieved. They seek valuable rather than predictable results. Here’s a roadmap to making the switch.
Microservices is an emerging approach to software development that breaks down complex applications into smaller components or processes. It embraces DevOps, complements agile, and can provide better scalability and resilience, among other benefits. But it also requires significant organizational change, and it isn’t a silver bullet; in fact, it can make a mess. Is it for you?
Top agile organizations favor a product-centric model of execution over a project-centric model. They chase value instead of predictability. Let’s look at what’s wrong with plan-driven projects, and why it’s better to organize your efforts along business capabilities, supporting capability teams instead of project teams.