Application of Methodologies for Project Success: Q&A

Saranya brings expertise in project management methodology, business processes consulting and change management. Saranya has led multiple internal and external projects successfully and effectively deals with challenges in high stake software implementations.

  Agile   Estimating  

In the webinar Application of Methodologies for Project Success, all of the project management methodologies in the market (waterfall, agile and lean methodology) were explored. The strengths and weakness of each methodology in a systems implementation and how to exploit the strengths to ensure a successful project were discussed. Participants walked away from the webinar with renewed insight, and below are some of the questions from that session:

1. Agile is about eliminating the need of extensive documentation. But I understand we even need to maintain documentation for agile as well.
I agree that even agile environments need some level of documentation. The most I have seen is logging and tracking backlog items and bugs. I haven’t specifically seen the overall scope, goals of the project, roles and responsibilities or changes ever documented.

2. How does this combination differ from waterfall split in several parts? What type of projects is this suitable for?
I am not familiar with what you are referring to when you say “waterfall split into several parts.” As I mentioned in the webinar, the methodology we used is suitable for projects where the requirements and technology solution can be known at the beginning of the project. If a project requires requirements to be uncovered as we go, agile or lean startup may be more suitable.

3.  How …

Please log in or sign up below to read the rest of the article.