Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  White Boarding Session
Previous Previous
 
Next Next
New Post 12/11/2012 11:11 PM
User is offline Kimbo
454 posts
5th Level Poster


Re: White Boarding Session 

Hi Dean,

If its just a maintenance function for the user you can probably just write one document. Record what the business requirements are, any business rules and the business domain (data). Define your use cases or user stories and then prototype your screens.

Its unclear from your post if there is more than one screen. If its a small number you can probably just draw up a prototype on the whiteboard. Maintenance functions are often very similar - standard CRUD functionality with the only difference being the data being maintained.

Kimbo

 
New Post 12/12/2012 2:29 PM
User is offline Jenny Nunemacher
3 posts
No Ranking


Re: White Boarding Session 

 The whiteboard is just the medium for capturing the discussion, usually with some sort of graphical representation. Whiteboards are good for not only creating mock-ups of new UI features, but you can also create context and data flow diagrams which help center the discussion and put up the so-called rails around the feature: What are you inputs and outputs? Who are your users? If you're trying to elicit details about process you might look at workflow/process analysis or possibly state diagrams for your data or UI.

More important than the "whiteboard" you need to go into the discussion knowing what your goals are, which questions need to be answered, and how you know when to stop. Also don't be afraid to be not done at the end of your allotted time. Discussion invariably raises additional questions which either need more time or investigation. Sometimes you can defer those, but sometimes they demand a follow-up discussion in order to meet the needs of your product.

Good luck!

 
New Post 12/13/2012 5:37 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: White Boarding Session 

Jenny:

Some really great comments about creating Data Flow Diagrams (including Context Diagrams) at the Whiteboard!    DFDs, especially for the first few iterations on a more complex projects, require rapid iternations.   No time for pretty diagrams using Visio or other software tools.  A BA needs to get up to the Whitboard and quickly iron out his/her more gross misunderstandings.  Thats how a BA makes a significant contribution to an Agile project!

"What are your inputs and outputs?".   THATS the $64 K question to ask that is over the head of the BPMN, Use Case, and Activity Diagram  crowds.

Tony

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

Community Blog - Latest Posts

Context:  Intro Change Request Definition Reasons for CRs Adaptive, predictive and mixed projects Flow of processing change requests Change Management Workflow Tools and Techniques 1. Intro  The World will never stop changing, as well as human needs and desires. The business environment evolves continually. An or...
For many people, a career in business systems analysis can be an ideal opportunity to use their skills in technology and business. Business systems analysts bring together the best of both worlds – technical know-how and business acumen – to help organizations become more efficient and effective. Here are some of the key benefits of pur...
There is no doubt in my mind that curiosity nurtures the mind when it comes to T shaped skills.  T shaped professional are specialist in something(the vertical line) and also have a wide range of skills and knowledge in a broad range of subjects(the horizontal line) and are are highly sought after in the workplace.  I’ve recently...

 






 

Copyright 2006-2023 by Modern Analyst Media LLC