Whitepaper: Introduction to Monte-carlo Simulation in Software Development

Posted by in Featured, Reference |

We have just completed the first of many whitepapers on technology expertise we wish to share. This whitepaper is on Monte-carlo simulation and its application to more reliable estimation and management of software development projects. Feel free to read and share this publication with your teams and management.

Introduction to Monte-carlo Simulation for Software Development – Forecasting and managing software development project risks & uncertainty

Abstract:
Monte-carlo analysis is the tool of choice for managing risk in many fields where risk is an inherent part of doing business. This paper examines how to use monte-carlo techniques to understand and leverage risk in Software Development projects and teams.

Introduction
For software development, it is often necessary to estimate a project upfront in order to get project approval, obtain budget and hire the correct team size and skill-mix. This is often at odds with the Agile development methodology where full upfront design and specification is avoided, and delivery happens in small iterations until a backlog is completed. The desire to work iteration to iteration and choose a finite level of work each cycle is compelling, and it does un-deniably bring value to production earlier than a pure waterfall approach.

However, the fact still remains that in order to provide any value to an organization, a finite minimum level of functionality (work) needs to be delivered by a preferred date, within a budget constraint; very few companies will sign off on a project that has no target date, and an open budget. Often delays incur high cost; not just development costs, but also as competitors launch new feature first, or take an increasing market share. Even with Agile teams it is important for any development manager or organization to be ready to answer the following questions on an ongoing basis –

1.    How much will this product cost to develop and deliver?
2.    What is the likelihood of releasing by date x?
3.    What resources do you need to hit date x (money equals people, so the question is often how much more money do you need to hit date x)?

This paper introduces a technique for answering these questions given the risks involved in software development and delivery. Monte-carlo analysis is a proven technique for determining the likelihood of an outcome in the face of many difficult to measure input criteria. Monte-carlo analysis doesn’t completely eliminate any risk, but it does give a much higher degree of satisfactory answer than the plain guesses and gut feel that is employed today (as to release date) in many software projects.

Troy.

Read More

Beta Testers Wanted for Kanban Simulator

Posted by in Announcements |

We are looking for beta testers for our Kanban simulation product. This beta trial will be on the installed version of our product, with an online beta coming soon. If you are interested please email Troy Magennis at troy.magennis@focusedobjective.com
We are finalizing the initial release now, and welcome all comments and suggestions. Take some time to look at the features, and let us know if you want to help.
Troy.
Read More

Kanban Simulator Demo – Short Video

Posted by in Reference |

This video shows the basic features of the Kanban Simulator we will be releasing for Beta shortly. We will be actively looking for companies and people willing to beta trial this tool, and if you are interested, please contact us for more information or email me directly: troy.magennis@focusedobjective.com
(Note: This video has no sound; Workplace safe!)

If you have any comments, please feel free to email me: troy.magennis@focusedobjective.com
Enjoy…
Read More

SimML – Modeling Language for Kanban and Scrum Teams and Projects

Posted by in Announcements, Reference |

We would like to introduce an XML specification for defining teams and projects that use Scrum and Kanban development processes. This file format is called SimML which is short for Simulation Modeling Language.

You can view the draft specification here.

SimML has the following features for modelling team and project data:

  • Specify Kanban columns (wip limits, cycle-time confidence intervals, names, etc)
  • Specify Defect categories (occurrence rate and override column cycle times)
  • Blocking Events (occurrence rate and cycle time confidence intervals)
  • Added Scope (occurrence and category. For example, scope-creep and refactoring)
  • Backlog

The file format also contains all of the information required for simulation, for example, what types of simulations to execute and how to format the results.

We will be announcing more features in this extensible file format over-time, and welcome other companies supporting the format as an input or export when needing to represent Kanban or Scrum teams and projects.

SimulationModelingLanguageforKanbanprojects.pdf

Read More