Many people think they can only choose between waterfall and agile for their project approach. But we can use criteria to help us decide the right approach for our project—even an unnamed, non-standard approach. When we choose an approach that manages our risks, we are more likely to succeed.
1123 items found
Question: I am going to head a team on a large, corporate project that will involve multiple teams. The problem is that we are not all going to be using the same methods of project management, and I am concerned about how we will be able to work together if we are not all following the same processes. Is it possible for various parts of the organization to work in different ways and still produce a good product?
Agile has been “going mainstream” for more than a decade, but supporting evidence was more in the eye of the beholder. Maybe now it’s really happening. A new State of Agile report found growing adoption rates outside of software development and documented success in areas such as visibility and alignment.
Is hybrid really the dominant approach? Recent surveys have suggested that hybrid is the dominant approach to project delivery. Is that really the case? And should it be the case? Let’s start by recognizing that not everyone has the same understanding of hybrid.
With some exception, gone are the days of fully defining the project’s scope followed by a comprehensive project plan. So too, however, is the expectation that the goals of a project can simply unfold as time passes. Let’s look at three scenarios…
A growing number of professionals must recognize that it is necessary for us to understand a core driver for this period of change: multiple technologies, which are evolving and bring with them unique capabilities. Is your workforce prepared for the disruptive change we will all face?
Prototyping, scrum, SAFE, kanban...it's easy to get confused these days. Here we walk through some of the main project methodologies used for IT projects today and give a little history of each—with some recommendations for when each methodology might be most appropriate.
Project leaders have a key role to play in innovation. It starts with giving teams the flexibility to be creative and develop unexpected results. Facilitating customer interaction helps teams explore what is actually needed and get in the mindset to deliver it. And stakeholders must be prepared for change and ambiguity, instead of predictability.
When customers are reluctant to embrace a project team’s agile approach, should the organization modify the approach to accommodate them, or should they press on and “prove” it is the best way to deliver what they want?
How can we meet the need for fast-paced, yet reasoned, innovation? As we face a changing, adaptive business environment, "compelling events" can help organizations achieve the vision of the product that they want, while also serving as an effective device for agile project teams.