Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Managing & Lead...  PM wants a deliverable list
Previous Previous
 
Next Next
New Post 1/7/2010 7:49 AM
User is offline oo3762
1 posts
No Ranking


PM wants a deliverable list 

Our PM has requested a list of delverables for the client (and him) to be kept informed of the items currently included in the project. This document will change periodically based on new requests to be added in and not only include enhancments scheduled for the release but also future enhancements currently in progress, i.e requirements gathering and BRS. The original idea was to post these to the Release Notes. I disagree with this since the Release Notes should include only those items implemented forthe release. What document should this deliverables list be included with?

 
New Post 1/7/2010 6:45 PM
User is offline Jarett Hailes
155 posts
6th Level Poster




Re: PM wants a deliverable list 

Hi 003762,

Could you be a little more specific about what exactly this document will contain?  Is it to contain all the business requirements for the scope of the project, system specifications, functional requirements, etc.?

To me this sounds like a living requirements document that also tracks the state of each requirement (in/out of current scope field as well as not started, in development, in progress, in system testing, in UAT, completed, etc. progress field).  This document will manage your overall set of requirements for the life of the project, and when the project is completed you can retain the incomplete/unmet requirements and pass them off to the sponsor so they can decide whether to develop a business case for a new project.

 
New Post 1/11/2010 8:04 AM
User is offline Brad
9 posts
10th Level Poster


Re: PM wants a deliverable list 

Depending on the methodology you are following, this information would fit well in a Iteration Plan.  However, if you are not planning on using iterations, you can still utilize this type document by calling it a Release Plan.  I would suggest keeping this document focused on the measurable, deliverable pieces of functionality the client is requesting, rather than the detailed requirements of each functional piece.  Based on my experience, clients and PMs get bogged down in the details of requirements, but respond well to status of functionality.  You can then utilize a traceability matrix to map the larger functional pieces to the detailed requirements pieces. 

Your Release Plan may include future releases, and therefore is a changing document.  You are correct that your Release Notes should include only those items actually delivered in the release.

Feel free to contact me if you would like an example template.

Brad Botz

[email protected]

Prime Proficiency


Brad Botz Prime Proficiency - BA Training and Information www.primeproficiency.com
 
New Post 1/11/2010 1:55 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: PM wants a deliverable list 

There are a couple of tools you could use to do this effectively.  My preference would be for a release plan, or at a more detailed level, a product backlog.  Both of these terms can be found on the www.scrumalliance.org website.

You could also use a feature list, or a product breakdown (aka product breakdown structure).  The Product breakdown is good because it maps tightly to a work breakdown structure, which should (could) be your PM's main work plan.

more info

Good luck.

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Managing & Lead...  PM wants a deliverable list

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC