Design and Development metrics/goals
I have been asked to set up a goal to reduce our ‘full development’ cycle time (from kick off to module is live) by 10%. Last year, we tracked the amount of total time for each module divided that by the ‘seat’ time of the module to what our average development/design time was. This help to compare modules that are 15 minutes to 1 ½ hours long. I was able to identify in the design process where time was over estimates and reduced the design part of the cycle time.
The challenge I am facing in reducing the ‘full development’ cycle time is from kick-off to storyboard sign-off from the SME & Module requestor/owner. These are usually the same person, but not always. Even though we have an agreed upon milestone timeline, we continue to get off track due to SME response for content and storyboard approval. These are product specific modules, so the pool of SMEs is limited. It is not that they don’t want to help, it more we are the low priority and many travel. Selling product and helping customers is their main job. We were giving them 3 business days to respond to storyboards, but increased it to 5 with smaller amounts of content to review/approve based on the tracking we did over the past year. We went from telling them it would take 4-5 weeks to 5-6 weeks for a module to be developed and live. This put the projected ‘live’ date closer to what actually occurred, but raised the red flag to put a metric/goal in place to get more modules developed.
Does anyone have any advice on:
1. How you track ‘full development’ cycle time and compare it when course range in ‘seat time’?
2. How to keep projects on track when SMEs are unresponsive due to priorities?
3. What do you track for development/design goals
Thanks in advance