Waqas, you have raised a very interesting question here. Normally a turn-key project would be a fixed price contract where scope is pretty much fixed. Then how can a turnkey project be agile? Generally my answer would be NO, a turnkey project cannot be agile. But what if it is an IT project with changing requirements. In such a case, the contract itself must describe explicitly how change in scope will be managed. If you think a bit more creatively, you will be able to see how and what can be done to make aturnkey contract agile. You may be assigned to develop a system but where and how it would be deployed would be decided later. Even the soecs of the system itself are liable to change continuously. Though tricky but possible. Saving Changes...
Francisco AbreuPortfolio Manager| Banco Central do BasilBrasilia, Df, Brazil
Wagas.
I have this problem in my IT projects.
The approach that we have used in this issue in my department was abolishing some agile concepts such as backlog list and time box, for example.
Personally, I DO NOT believe in the time box concept, because I don’t know clients that accept “half product” because the time has gone. The contracts that I know consider “escope” instead “time”. Except body shopping . . . but in this case they don’t turn key projects what conduct us back to start . . .
In my department we handled agile projects with outsource companies in this way:
1. Software Provided Outsource Company is contracted for unit value measured in FUNCTION POINT (FP) or STORY POINTS (SP).
2. Project Team accomplishes a detailed requisites analysis.
3. These requisites were divided in modules
4. These modules are quantified in FP or SP
5. This quantity is multiplied by unit value contracted. In this step one formal SERVICE'S ORDER is opened and sent to outsource company.
6. Each module is developed under the agile concepts such as ATDD, Kanban Controls, Burndown Graphics, Agile Teams, Banchs, etc . . .
In this way we are able to maintain the scope’s control what are sent, received, homologated, and deployed. . .
We know we don’t are being “pure” agile, but we believe that results are much more important . . . and we are getting them . . .
I hope I have contributed
Saving Changes...
Francisco AbreuPortfolio Manager| Banco Central do BasilBrasilia, Df, Brazil
Waqas.
In my previous post I spelled your name in incorrect form.
I"m so sorry about that. Saving Changes...
Pravin thanks but the issue is that when i sub divide the project i do not have a definitive outcome, i mean that phases are overlapped. Saving Changes...
Suhail Sb, exactly my point. When ever i want to implement in Roll Out which is turn key then due to over lapping phases i am not able to implement but in other industry as you mentioned in IT, agile can be implemented.
I have tried and in making it agile focus from project deliverable are out. Saving Changes...
Thank you Francisco for detailed reply.
I feel that implementation of agile is more in IT and like you said that results matter so we can not implement agile completely. Saving Changes...
No worries Francisco for the spells.
cheers. Saving Changes...
Ashok GuptaGroup Manager| Mercer Consulting India Pvt LtdNew Delhi, Delhi, India
I strongly believe that Agile approach can be applied to even fix-bid, fix-scope projects as well, it may not be true Scrum Agile but could still be iterative agile of some sort. Lets take an example here (and please add /share your inputs) -
Lets assume that I am given a turn-key project to run that has $1000 budget and it is about constructing a room within 20 weeks.
I can start creating a backlog with help from a business lead (=PO) as I interview stakeholders/business teams to gather requirements, rough estimate could help me plan how many iterations I can have and how i would like to time box them.
Examples (4 weeks ITR each) -
ITR1 - work with vendors, contract, procure material, lay out base
ITR2- construct 4 walls
ITR3- construct roof, fittings etc
ITR4 - paint it all, finishing etc
ITR5- handovers, closure tasks, turn the key over :)
Waqas, as mentioned by Suhail, Turnkey project is supposed have detailed plan. It is not practicable for agile in non-IT projects. Within the project, you can try to follow agile process, which will help to monitor the progress on daily basis. Saving Changes...
