Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  White Boarding Session
Previous Previous
 
Next Next
New Post 11/28/2012 6:03 PM
User is offline JDeanBA
2 posts
No Ranking


White Boarding Session 

 Hi,

I have been tasked to facilitate a whiteboarding session to gather requirements.  We have a web application & we need to develop a maintenance function for the user.  I am new to business analysis & wanted to find out what sort of documents should be produced from the session.  Also if there are examples I can build upon.  Any and all help is greatly appreciated.

 
New Post 11/29/2012 5:28 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: White Boarding Session 

Hi:

Use the white board to quickly create just barely good enough models.   System behavior analysis drives system data analysis, so the first order of business is to create and walk through behavioral models.   

If your system is simple, then you can jump right into sequence based behavioral modeling techniques (BPM and Activity Diagrams).   If your system is complex, then you need to model at various levels of abstraction using decomposition to handle the complexity.   This is where data flow diagrams come into play.   With DFD's after you decompose a system far enough down, then you switch over to sequence based modeling to handle modeling  the "system in the small".

After you have scoped out the essential behavior of the system, then use the white board to create just barely good enough data models, like ERDs.

 
New Post 12/5/2012 9:01 AM
User is offline dldelancey
61 posts
8th Level Poster


Re: White Boarding Session 

Your deliverables should be defined by the needs of the people who will consume them.  Identify those people and ask them what documents they need.  Typically, the consumers are developers, testers, release managers, operations, security, product owners, change managers, etc. etc. etc.  Having said that, there's several ways that could go depending on the development methodology in place (or lack thereof).

Is this a contractual arrangement with an external client?  If so, check the contract and/or the statement of work.  Your deliverables hopefully are stated there.  Keep in mind, however, that what you are contractually obligated to deliver may not actually be what the consumers of the deliverables need.  Which brings me back to... identify those people and ask them what they need. 

If your team is doing waterfall development, you're likely to be document heavy, and you probably need requirements specs and such.  If your team is agile, you're likely to be document light and may only need user stories and such. 

 
New Post 12/7/2012 6:59 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: White Boarding Session 

didelancey said:  "If your team is doing waterfall development, you're likely to be document heavy, and you probably need requirements specs and such.  If your team is agile, you're likely to be document light and may only need user stories and such."

Unfortunately, this confuses bad waterfall with waterfall.     Good waterfall has always been "just barely good enough" documentation.   I know that bad waterfall is much more common, but, just like good Agile is not "hackers gone wild" , good waterfall is not "heavy documentation"

Tony

 

 
New Post 12/10/2012 12:43 PM
User is offline dldelancey
61 posts
8th Level Poster


Re: White Boarding Session 

 Tony Markos wrote
 

didelancey said:  "If your team is doing waterfall development, you're likely to be document heavy, and you probably need requirements specs and such.  If your team is agile, you're likely to be document light and may only need user stories and such."

Unfortunately, this confuses bad waterfall with waterfall.     Good waterfall has always been "just barely good enough" documentation.   I know that bad waterfall is much more common, but, just like good Agile is not "hackers gone wild" , good waterfall is not "heavy documentation"

Tony

 

You will note my use of the word likely.  Unfortunately, bad waterfall is more likely than good.  But that is entirely beside the point of the original poster's question. 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  White Boarding Session

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