Project Management Central
|
Please login or join to subscribe to this thread
|
||||
|
||||
Luis -
Integrating a deliverable is different than what the PMBOK Framework would term "Integration Management". The latter relates to the orchestration work of the PM - the glue binding all the other knowledge areas together. Your question is more specific about building the product/service/result requested by the stakeholders. Depending on the context of the project scope, integration might happen continuously (e.g. a software application is constantly being built and tested as code changes are happening) or on a regular basis (e.g. at the end of an iteration or at regular scheduled intervals). The former is ideal as it enables as short a product/service/result feedback loop as one could hope for. The latter can increase the risk of building the wrong product or building the product wrong. Kiron ...
1 reply by Luis Branco
Dec 07, 2022 4:43 AM
Luis Branco
...
Dear Kiron
Thank you for your comment. It really is different when we are approaching the subject from the perspective of processes and from the perspective of the product
I agree with Kiron.
Network:720
Integration at the end of each iteration or after multiple iterations is a fundamentally flawed philosophy. Integration begins in change management planning rather than after code is released.
When there are multiple software applications working together, some may be developed independently. Some might require synchronized change incorporation in defined blockpoints. Even a sprint of very limited scope still has a desired outcome. Integration activities following the completion of an iteration should be verification of functionality and requirements planned in advance, and identification of unexpected behavior that must be dispositioned and the fixes planned for a future iteration.
Integration is part and parcel of all things agile. It should never be a separate task or work package.
Agree with Stéphane comments. Integration management is inbuilt into Agile.
For example in Crystal which is a lightweight Agile methodology seven important properties are as follows : 1. Frequent delivery 2. Osmotic communication. 3.Personal safety 4. Focus 5. Easy access to experts. 6. Technical environment with automated tests, configuration management and frequent integration. Dec 06, 2022 7:46 AM
Replying to Kiron Bondale
...
Luis -
Integrating a deliverable is different than what the PMBOK Framework would term "Integration Management". The latter relates to the orchestration work of the PM - the glue binding all the other knowledge areas together. Your question is more specific about building the product/service/result requested by the stakeholders. Depending on the context of the project scope, integration might happen continuously (e.g. a software application is constantly being built and tested as code changes are happening) or on a regular basis (e.g. at the end of an iteration or at regular scheduled intervals). The former is ideal as it enables as short a product/service/result feedback loop as one could hope for. The latter can increase the risk of building the wrong product or building the product wrong. Kiron Thank you for your comment. It really is different when we are approaching the subject from the perspective of processes and from the perspective of the product |
||||
Please login or join to reply
ADVERTISEMENTS
|
"If you would be a real seeker after truth, it is necessary that at least once in your life you doubt, as far as possible, all things." - Rene Descartes |
