Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.
Be Prepared for Stakeholder Interviews
In this Episode of the Business Analyst Mastery podcast I’ll talk about:
- A comment about one of my Business Analyst articles at modernanalyst.com
- Stakeholder Interviews
Download thisBusiness Analyst Mastery Podcast Episode
{ 2 comments }
Hey, thanks for the great podcasts.
Just regarding the comment you received in relation to activity diagrams and the ‘appropriate’ usage. I wholeheartedly agree with your response but would even go a bit further and say that you can use any diagram in any way you want, even outside of the ‘formal’ usage specifications.
In my opinion the purpose of diagrams is to convey meaning. In the case of writing software requirements for example, it’s to convey requirements or workflow etc. So I think to be constrained by a formal usage specification of UML or the like just for the sake of conforming to the language is shooting yourself in the foot if it’s at the expense of clarity and purpose of your diagram.
Sometimes we get so caught up in our own brilliant documentation that we forget the point! The point is to get the meaning across, so whatever works, works!!
Cheers,
Karen
Karen,
Thanks for the comment.
I’m a big fan of getting the job done. In the end, they don’t remember our brilliant documentation, as you put it, they just remember that the job got done or didn’t get done.
Comments on this entry are closed.
{ 1 trackback }