I agree with every point of the Agile Manifesto and with almost all the agile practices. I believe that following an agile software development process is the right way to address most of the problems that we see in several projects nowadays.
So, why do I decide to take a PMI© Certification course?,.. well, I wanted to know more about PMI©, learn from it, modify it, adapt it to agile practices and write about everything I disagree/agree with. I just want challenge myself!
The course was divided in sections, one for each PMBOK© chapter. So I can read each chapter before class and prepare questions or topics for discussion in class. Yeah, that will be fun!
Well, as part of the Certification course my group has to develop all the documentation for a software development project reusing some templates that we received in the first day of class. This week, we had the first preliminary presentation of Project Charter and Preliminary Project Scope Statement documents. While I was looking the Preliminary Project Scope Statement template, I had a doubt about project phases because the template assumes sequential project phases and my partners defined them as: analisys, desing, implementatión, testing. OMG that’s waterfall!!!
I asked about how can I show clearly that I’m following an iterative process in the Preliminary Project Scope Statement but I didn’t receive a clear answer. Someone told me that PMBOK© assumes that project phases are sequential. Argggg!,… waterfall!!!
At night, taking a closer look in Chapter 2 – Section 2.1.2 – 3rd Paragraph, I found that PMBOK© uses as example an information technology project with iterative project life cycle!. In conclusion, PMBOK© assumes that most of the projects have sequential phases but there are exceptions like information technology projects using an iterative life cycle.
So it could be interesting to develop a template for Preliminary Project Scope Statements that assumes parallel and sequential phases and a mix of them.