Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Be a Better BA<br />The challenge of the <br />Requirements Workshop<br />
How hard could it be?<br />
Our intrepid Business Analysts has invited five project stakeholders along for a requirements verification workshop.<br />...
Let’s take a look at how complex this discussion could get.<br />
R1<br />Our heroine announces Requirement 1 and reads it out. It is simple, straightforward and there is little in the wa...
R1<br />R2.1<br />R2<br />Requirement 2 is read out and kicks of a lively discussion about the definition of the word “Sha...
R1<br />R2<br />R3.1<br />R3.2<br />R3<br />By Requirement 3 everyone is on a roll. Let’s really get into the guts of thi...
Let’s stop and look at how this conversation is flowing.<br />
R1<br />R1<br />R1<br />R2<br />R2.1<br />R2<br />R3.1<br />R3.2<br />R3<br />
3 Simple requirement statements. <br />And this isn’t even a very thorough conversation. Imagine what it will look like a...
What’s going to happen in this room?<br />
What we need…<br />
Pick your methods<br />Lots of people<br />A professionally facilitated and agenda run meeting, time boxed with any detail...
Read more at<br />www.BetterProjects.net<br />
Upcoming SlideShare
Loading in …5
×

Ba tips: the complexity of workshops

3,449 views

Published on

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

License: CC Attribution License
no profile picture user

  • Login to see the comments

Ba tips: the complexity of workshops

  1. 1. Be a Better BA<br />The challenge of the <br />Requirements Workshop<br />
  2. 2. How hard could it be?<br />
  3. 3. Our intrepid Business Analysts has invited five project stakeholders along for a requirements verification workshop.<br />She wants to get endorsement on the next 7 requirements the team are working on.<br />
  4. 4. Let’s take a look at how complex this discussion could get.<br />
  5. 5. R1<br />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.<br />Two stakeholders feel they have something to say on this topic (maybe just so they can feel useful.)<br />Everyone quickly endorses the requirement.<br />
  6. 6. R1<br />R2.1<br />R2<br />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.<br />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.<br />
  7. 7. R1<br />R2<br />R3.1<br />R3.2<br />R3<br />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.<br />
  8. 8. Let’s stop and look at how this conversation is flowing.<br />
  9. 9. R1<br />R1<br />R1<br />R2<br />R2.1<br />R2<br />R3.1<br />R3.2<br />R3<br />
  10. 10. 3 Simple requirement statements. <br />And this isn’t even a very thorough conversation. Imagine what it will look like at number 7!<br />
  11. 11. What’s going to happen in this room?<br />
  12. 12. What we need…<br />
  13. 13.
  14. 14. Pick your methods<br />Lots of people<br />A professionally facilitated and agenda run meeting, time boxed with any detailed discussions being broken up into smaller facilitated groups<br />Lots to talk about<br />A <br />conversation<br />One topic<br />Just you and me<br />to match your needs<br />
  15. 15. Read more at<br />www.BetterProjects.net<br />

×