Hi, I'm Business Analyst in the datawarehouse area. Me and my team are collecting Business requirements and translate them to new Data fields that are  added to our DWH. The Problem we are facing is the lack of having a proper progress Tracking. We have a process split into different phases (like collecting requirements, analysis, datamodel Design...), but we cannot sufficiently track the phases. For example, we have 300 new fields spread over 20 tables in different Business areas and wie have 10 weeks to finish the analysis phase. Wie cannot simply do a linear forecast by saying, that we finalize 30 fields per week. There are always ongoing discussions with many stakeholders and it may happen that in week 1 we finalize 5 fields, but in week 2 40 fields and so on. So its not really straight forward. What I am looking for is a general framework of how to measure the progress of such pure data-driven requirements. The ideal situation should be, that at any point in the requirement-lifecycle we are able to report how we proceeded so far (in %) and, more important, if we can meet the next deadline and how much person days it will take.

Any idea? 

Thanks, Fred

Hi NitWitNick,

thanks for your answer. I forgot to mention that we are currently using a KANBAN board (both virtually and physically) to manage our requirements. In this board we have incorporated all our phases in the requirement-lifecycle, including start and end dates for each.

My problem is that I am not able to measure the progress between start and end date of one phase properly. If I want to know the status it's either "initial", "in progress", or "done", but out of these status I cannot do a completeness tracking in %.

In a nutshell, I want to have a feeling at any point in time, if we can realistically meet the next deadline or, if not, how many additional effort would be needed to do so.

Thanks,

Fred