A few thoughts on identifying use case actors and a job-aid that may help simplify the effort.Read More
Month: May 2008
I’ve long been of the opinion that involving as many stakeholders in the project as early as possible is a key to successful business analysis, and, more importantly, to successful projects, and have said as much in a few of my posts on this site.
Jim Highsmith, in the book Agile project management : creating innovative products, thinks that the reason projects tend to have so much documentation and so few results is that:Read More
- Tweets of the Week – 20180713
- The Real Value of Visuals in Solution Delivery – A Reprise
- Hippocrates on Clarity of Language
- The Book, The Movie, and the Business Document
- Interview with Ryland Leyton, author of “The Agile Business Analyst”
- John Dewey on Starting with a Problem to be Solved
- Business analyst, these are the reasons your project will succeed
- Four Critical Components of a Meeting Invitation
- Benjamin L. Kovitz on Requirements
- Business Analysts and Grammar Police
- Visionary Leadership and You
- Alistair Cockburn – Agile is an Attitude
- Business Analysis Success is . . .
- Harold Evans on Creating Understanding
- The “Obviousness” Danger that Kills Projects
- Jabian Journal and Visual Communication
- Distinguishing between Business Rules and Software Requirements
- Roughly Right, or Precisely Wrong?
- 6 Guidelines for Building a Reputation with Your New Employer
- Why Stakeholders Don’t Tell You Everything