A Guide to Escalation in Project Management
By Deepali Bhadade
While most of project management plans or communication management plans have an escalation mechanism defined; in reality, very few project managers make an effective use of the escalation mechanism. Many of them try to avoid escalations in the fear of conflict; some overdo it for every next problem in the project. Both these approaches are harmful for projects. Escalating a project problem at the right time, to the right person with the right amount of information is an art to be cultivated by good project managers. This guide focuses on good practices and tips on effective escalation for project benefit.
The general meaning of Escalation is: Increase in magnitude or intensity by bypassing the immediate person.
Applied to the project context, escalation is generally a formal process to highlight the issue at hand to a higher authority as per the escalation mechanism defined for the project. Read the Complete Article
Make Your Waterfall More Agile
By Deepali Bhadade
Lately there has been huge discussions around waterfall vs agile for software development and which is the best way. While the answer to this is very context driven, there are pros and cons for adopting either of them. At times, due to some compelling factors, a project cannot fully adopt agile methods – rather classic waterfall methods seem more suitable. This write-up is focused on highlighting the best practices that waterfall development can adopt to overcome its peculiar challenges.
Adopting Agile practices in Waterfall
Many-a-times, due to compelling reasons like fair requirements clarity, customer’s reluctance for greater involvement in development, less experienced / distributed project team, defined workflows, multiple organizational stakeholder involvement, the predictive waterfall method is preferred for software development project.
This traditional way of developing software has its own advantages such as:
- Easy to understand and follow as it is sequential in nature
- The plan based approach brings discipline and predictability
- Supporting documentation lessens the person dependency
- Established protocols of communication helps in multi-organization stakeholder interaction
- Provides room for learning curve for the less experienced team members
- Risks related to schedule, skill gap, unplanned leaves can be easily absorbed with long delivery cycles
However, there are several challenges or limitations that software developers face while executing projects in waterfall method. Read the Complete Article