Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  How Do Project Managers Determine Due Dates?
Previous Previous
 
Next Next
New Post 6/12/2008 3:51 PM
User is offline Tony Markos
493 posts
5th Level Poster


How Do Project Managers Determine Due Dates? 

All:

On another thread, someone gave a link  to an article that compares Project Mgr and BA responsibilities.    That article, as is often done, states that Project Mgrs do the scheduling.  However, from what I have seen, the individual who has the strongest understanding of the "As-Is" is the one who should be setting due dates.   I have never been exposed to a PM who came anywhere close to fitting this bill.  

Can anyone explain to me what inputs a PM uses in deciding due dates\schedules?  

Tony

 

 
New Post 6/12/2008 10:18 PM
User is offline Jarett Hailes
155 posts
6th Level Poster




Re: How Do Project Managers Determine Due Dates? 

Hi Tony,

Every good PM I've ever met rarely makes their own estimates - they rely upon the expertise of the team leads from each respective group (BAs, development, testers, etc.) to judge how long their team's tasks will take.  In a phased project, they may use what's calling a 'rolling wave' estimate method, whereby they get the BA team to estimate how long it will take to do detailed BA tasks, and only get high level, broad estimates for future work since development time will be greatly dependent on what the BAs uncover and what sort of requirements are signed off on.

The other method, of course, is WAG (Wild Ass Guessing).  Most PMs I know have had to resort to this at one point or another, based on their experience on similar projects in the past.  Ideally though, they're asking the experts on the team how long it will take to do their work, then simply rolling that information up into a comprehensive project plan/work breakdown schedule.

 
New Post 6/13/2008 9:44 AM
User is offline David Wright
141 posts
www.iag.biz
7th Level Poster




Re: How Do Project Managers Determine Due Dates? 

A very common situation is the internally or externally fixed due date. For example, a new system is needed to support peak season for a company, like Christmas for most retailers. Miss the date, no point in having done the project. Meeting a government legislated deadline is another case.

The key is not to freak out, but to essentially define what can reasonably delivered in the set timeframe, starting with a given set of resources. Use  a rule-of-thumb like 25% analysis, 50% development, and 25% testing to divide up the timeframe. Work with the experts to estimate what can be created in such a timeframe. review that with the sponsor; if its not enough, try adding more resources but knowing that there is an upper limit on resources before adding more actually slows things down. Get creative, figure out what can be done in parallel, and have parallel teams/projects.........

Again, the key is not to say that fixed dates are not reasonable, but to work with the business to agree on what can be delivered by a fixed date. I have found that it is almost never completely what is wantedd, but it is enough to meet immediate needs, then add to it in another go-round.


David Wright
 
New Post 6/13/2008 6:08 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: How Do Project Managers Determine Due Dates? 

 larimar wrote

Hi Tony,

Every good PM I've ever met rarely makes their own estimates - they rely upon the expertise of the team leads from each respective group (BAs, development, testers, etc.) to judge how long their team's tasks will take. 

And good team leads will ask their team how long things will take.  Note this requires a team to know what activities they are going to do, and so some panning has to take place first.

 
New Post 6/13/2008 6:10 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: How Do Project Managers Determine Due Dates? 

[QUOTE]larimar wrote

Hi Tony,

 In a phased project, they may use what's calling a 'rolling wave' estimate method, whereby they get the BA team to estimate how long it will take to do detailed BA tasks, and only get high level, broad estimates for future work ....

[/quote]

An excellent way to accomodate uncertainty in the future. You can learn more on tis topic from Johanna Rothman's blog.

Also - anyone care to comment on agile project requirements planning and management procsses for BAs?

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  How Do Project Managers Determine Due Dates?

Community Blog - Latest Posts

Ekaterina Barabash
Ekaterina Barabash
I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important.  And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...
1 Responses
Dan Tasker
Dan Tasker
I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...
2 Responses
Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses




Latest Articles

What Does a Technical Business analyst do?
Feb 17, 2019
0 Comments
The function of a technical business analyst is to bridge between business and technical teams. This can be undertaken in various forms. First, the br...
Featured Digital Library Resources 
Copyright 2006-2019 by Modern Analyst Media LLC