Risk Analysis – Integration plan (part 2)
October 1, 2009 3 Comments
Every person has a different risk profile. This is the willingness of that person to take a chance to achieve a reward versus the probability of failure. The amount of risk we are willing to take seems to be correlated to the reward promised and the time frame associated to it (i.e. will I get teh reward tomorrow, in 2 or 10 years). Risk profiles of companies are somehow a weighted average of the risk profiles of their employees. Hence, different companies (even in the same market segment) have different risk profiles.
A company looking to engage with a specific version of the Symbian Platform has to decide how early to start development. The earlier you start the most opportunity you have to influence and contribute to how the platform is shaping, however the risk associated with it is the impact of ongoing changes to the code line. Here is some tools your might consider to help your decision making process:
Analysis of Key Features
I previously described the concept of key features. Now, through the integration plan, we are providing high level tools to understand their implementation progress. Firstly, here is a graph of key features integrated per bi-weekly window:
This will provide you with an indication of how much disruption are you likely to see each release. However, it is harder to understand from the same graph how close the release is from completing the main functional churn.
A burndown-like chart will be made available also with the integration plan. This might also be taking into account when deciding the best timing to engage with the platform development.
The above pictures provide a partial view of the changes (the most disruptive ones) that are planned for the release based on contributors latest updates. However, it does not aim to track every single change and it also gives the same weight to every submission. To complement this information it is important to look for an indicator that is more concrete – Code!
We are implementing a set of metrics around the platform, including code churn between kit releases. The chart below is a mock-up (not based on real data) of the reports that we will regularly provide, starting before the end of the year.
Talk to us
Ultimately, the tools mentioned here are only indicators that might help you, but if you have specific concerns get in touch with the delivery team. I am on skype at victorp.symbian, ping me and we can have a chat.