Mohammed AhmedSr.Project Manager| MDS For Computer SystemRiyadh, P.O.Box 1223, Saudi Arabia
requires a more iterative, integrated, and collaborative approach than in traditional acquisition programs. Contrary to the myth that Agile is an undisciplined approach that downplays cost aspects, cost estimation is a critical activity in programs that use Agile practices. Saving Changes...
Sort By:
Mohammed AhmedSr.Project Manager| MDS For Computer SystemRiyadh, P.O.Box 1223, Saudi Arabia
How Does Agile Impact An Organization? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
System thinking is one of the foundations of Agile. So, because organizations are open and adaptable systems, the whole architecture is impacted. But nothing new below the sun. The same with Lean or any other approach an organization needs to implement to put in practice the defined strategy. Saving Changes...
1. With variable costs such as labor, cost estimating might be based on the per work item or per iteration (e.g. Scrum) based cost. For other costs, it would be similar to predictive approaches.
2. Cost of delay is an important consideration when prioritizing what a team works on first.
3. You could take the approach of fixing costs with a bit of upfront discovery assuming the team has sufficient knowledge of the work to be done that a minimally sufficient output can be produced within the cost envelope. However, as uncertainty increases, the greater the likelihood this cost ceiling might not be valid.
4. A progressive costing model might address the risks in #3 by focusing on a single release only and making commitments on a rolling wave basis.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Mohammad
Agile Estimation and Lean Budgeting/Funding is far more better than traditional approaches but of course it depends on the type of project.
In Agile, you do high level estimates at the outset and refine those estimates for every release. Like Kiron mentioned: Progressive Costing.
RK Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
I find that we too quickly think about "costs", and by costs I mean currency (dollars in my case). We should really start with scope followed by effort required (resources) then we can apply costs. Regardless of the 'environment' one needs to know what objective one is trying to accomplish and how one is to go about accomplishing that objective. Progressive costing, as introduced in a previous comment, is the process of taking small bites but you still need to know the scope of that bite and the effort required. One can do this by task (deliverable) or by time period (day, week, month) ["how much effort will it take to ..." vs "what can we get done in one week/month"]. Then you cost the effort by applying the cost of resources.
I really don't see much difference between between estimating for traditional project delivery versus Agile. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Technically, your cost should be set at the level of iteration. Given a set number number of team members and a set number of days in your iteration, your iteration cost will remain the same. (I'm simplifying here. I know there are other costs, variable or not, that may be involved.) If you want a finer cost breakdown, I suggest you distribute the iteration cost over the iteration backlog items using their relative estimates (i.e., story points). Saving Changes...
Community Champion
