Ba tips:  the complexity of workshops
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Ba tips: the complexity of workshops

on

  • 2,974 views

When Business Analysts take their analysis and recommendations to stakeholders, we often use workshops. There is a trap in the workshop. You can only fit so much communica

When Business Analysts take their analysis and recommendations to stakeholders, we often use workshops. There is a trap in the workshop. You can only fit so much communica

Statistics

Views

Total Views
2,974
Views on SlideShare
2,392
Embed Views
582

Actions

Likes
2
Downloads
89
Comments
2

3 Embeds 582

http://www.betterprojects.net 578
http://translate.googleusercontent.com 3
http://webcache.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Dave, I know what you mean. Once you have learned some technique you manage the crowd. But not everyone has learned the techniques, and maybe other methods can be more effective as well?
    Are you sure you want to
    Your message goes here
    Processing…
  • I do requirements sessions all the time. They are not flowing conversations between a group of people, they are directed (by me) to discuss process and information, from which we elicit requirements.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Ba tips: the complexity of workshops Presentation Transcript

  • 1. Be a Better BA
    The challenge of the
    Requirements Workshop
  • 2. How hard could it be?
  • 3. Our intrepid Business Analysts has invited five project stakeholders along for a requirements verification workshop.
    She wants to get endorsement on the next 7 requirements the team are working on.
  • 4. Let’s take a look at how complex this discussion could get.
  • 5. R1
    Our heroine announces Requirement 1 and reads it out. It is simple, straightforward and there is little in the way of exceptions to the core requirement statement.
    Two stakeholders feel they have something to say on this topic (maybe just so they can feel useful.)
    Everyone quickly endorses the requirement.
  • 6. R1
    R2.1
    R2
    Requirement 2 is read out and kicks of a lively discussion about the definition of the word “Shall”. Additionally there is an important and common ‘exception to the rule’ that is discussed robustly by most of the stakeholders.
    It seems that putting this new function in an IT system is going to be a challenge for some people who like the fuzziness of the rule today.
  • 7. R1
    R2
    R3.1
    R3.2
    R3
    By Requirement 3 everyone is on a roll. Let’s really get into the guts of this issue. There are two points e want to really nail here.
  • 8. Let’s stop and look at how this conversation is flowing.
  • 9. R1
    R1
    R1
    R2
    R2.1
    R2
    R3.1
    R3.2
    R3
  • 10. 3 Simple requirement statements.
    And this isn’t even a very thorough conversation. Imagine what it will look like at number 7!
  • 11. What’s going to happen in this room?
  • 12. What we need…
  • 13.
  • 14. Pick your methods
    Lots of people
    A professionally facilitated and agenda run meeting, time boxed with any detailed discussions being broken up into smaller facilitated groups
    Lots to talk about
    A
    conversation
    One topic
    Just you and me
    to match your needs
  • 15. Read more at
    www.BetterProjects.net