Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, IT Project Management, Scrum
What is Half Agile? Is this type of methodology really exists ?

I always followed waterfall model for project management, And now started to Agile methodology.
How is half agile process possible ?
Sort By:

The two work well together. Waterfall is your project roadmap to a destination. Use Agile to get you to that destination by satisfying all the tasks on your roadmap by not being hung up on dependencies. There always will be dependencies, but with an Agile mindset you should look for opportunities to knock out tasks in your roadmap not necessarily in sequential Waterfall order when possible.

Using Agile without Waterfall is a recipe for disaster. Waterfall provides a definition of a path of tasks. Agile provides flexibility.

Agile is not a method/methodology. You can use Agile with any type of process life cycle, waterfall for example. What people have to understand is: with basement in approaches (Lean, Agile, etc) you can use any life cycle model (predictive or adaptive), any life cycle process based on life cycle models (waterfall, iterative, sequential, incremental, etc), any method based on those life cycle process (SDLC, Spiral, V, Scrum, DSDM, etc). You can mix all this based on your actual organizational state mainly the architecture.

John -

What's important to recognize is that agile or waterfall are not mutually exclusive choices. There is a continuum of options from fully waterfall (which is extremely rare) to fully agile (which is equally rare) - most projects fall somewhere in the middle.

The wisdom is in a PM supporting their team in discovering what is the "right" set of practices to use for a given project's context within organizational and regulatory constraints.


Remember, Agile is a mindset. You can be agile in a waterfall environment. What you're referring to is many organizations choosing to blend 'traditional' concepts with the popular Agile movement (though not new) - may be called Hybrid, Scrumfall, etc.

The important thing to keep in mind is that no matter the how, the goal is to provide a successful deliverable to the customer, matching the needs of the customer, aspects of the project, and available toolsets.

I prefer to think of a sliding methodology scale with pure agile at the opposing end to pure waterfall. I find the majority of initiative deliveries usually fall somewhere in the middle; the key is early recognition of whether the hybrid approach required is more waterfall or more agile.

John, the key thing is to slice your scope in pieces the team can deliver in timeboxed iterations. Slice the scope pieces according to team velocity and what the team is able to plan realistically and can manage in order to deliver the project customer value (product features, IT system features etc.) in a constant way of delivery. By this you achieve early visibility and mitigate risk. As Sergio and others emphasized, it is independent from the project life cycle. Important is agile mindset and communication, communication, communication... (working together as ONE team).

Thanks all .

Please login or join to reply

Content ID:

"Whatever does not destroy me makes me stronger."

- Friedrich Wilhelm Nietzsche



Vendor Events

See all Vendor Events