Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Progress Tracking
Previous Previous
 
Next Next
New Post 8/18/2016 11:28 AM
User is offline FredMM
3 posts
No Ranking


Progress Tracking  

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

 
New Post 8/18/2016 2:27 PM
User is offline NitWitNick
258 posts
5th Level Poster


Re: Progress Tracking  
I've used KANBAN for all to see where people are on a project ... make a Kanban Board and hang it on the wall ... and use post-its to put stuff up and move items to a different stages ... whatever. We have used Adhesive Tape to make a big board on a wall ...


You can break down what has to be done by priority, in different sprints.

Your team can see what is lined up, what to do, who has what, progress, etc ... make what columns you need.

Everyone can walk by and visually see where the project stands ... and you can transfer that info over to documentation for your manager ... he can walk by and look without bothering you.


Read the article and look at the pictures to get an idea.




http://kanbanblog.com/explained/

https://www.google.com/search?q=%22kanban%22&num=50&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwjWvK658svOAhUW2GMKHcrADIsQsAQIeQ&biw=1024&bih=645
 
New Post 8/18/2016 11:39 PM
User is offline FredMM
3 posts
No Ranking


Re: Progress Tracking  

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

 
New Post 8/20/2016 6:48 AM
User is offline NitWitNick
258 posts
5th Level Poster


Re: Progress Tracking  

What about your daily meeting (Scrum, etc) to see where each team member is on their part ... whats been done, what will they be doing today, any hold ups, problems, need help to meet deadlines, etc ?

You might be able to catch a problem before the project goes past a deadline ... and find a solution.

You can keep track of that "In Progress" in better detail.

 
New Post 8/22/2016 10:04 AM
User is offline FredMM
3 posts
No Ranking


Re: Progress Tracking  
Since I only know the scrum-approach from software development, I didn't take it into account for business analysis. But thanks for the hint, I will try to introduce daily stand-ups. 
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Progress Tracking

Community Blog - Latest Posts

Arash
Arash
Let me start by saying that a business rule is far more granular than a business decision, and that the two should never be confused. Today, it is an unfortunate fact that some vendors would have potential clients believe that there is synergy between business rules and business decisions. Perhaps this is because in an effort to differentiate one b...
0 Responses
LN Mishra, CBAP
LN Mishra, CBAP
Traceability is one of the lesser understood aspects of business analysis. It is indeed quite hard to maintain good traceability unless automated. This is why BABoK® warns us being theoretical about traceability. In this article, I would like to explain traceability concepts with help of an example. BABoK® definition of traceability: ...
4 Responses
Hitendra 01
Hitendra 01
Most IT jobs have a clear, specific job description and career path. However, the business analyst career path tends to vary, as do the descriptions from job to job. The business analyst career path is best. Because, “There are career tracks that zigzag back and forth between IT and business. Someone might start as a business analyst, and the...
0 Responses




Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC