Jun
19
On Clarity of Content
June 19, 2006 |
I’ve added the BA BoK (Official) category to this weblog for your benefit.
A post in that category reflects an official announcement or other statement. For instance, if I post about the definition of a requirement in that category, I’m writing on behalf of the team and the IIBA, and the post reflects agreed-on content. Naturally, that material is still subject to future revision and the like, but it is official at the time of posting.
The BA BoK (Opinion) category is just working notes, suggestions, ideas, or thoughts. When I post to that category I’m speaking only for myself as an individual. Those posts should not be taken as anything more than what I think, and there is no guarantee that such material will be reflected in the final product.
Comments
What I'm Reading- Do You really Believe in What you Do?Requirements Defined - Seilevel's Software Requirements Blog
- C.R.A.C.K. Requirements managersBetter Projects
- ‘IT has no inherent value’IT Project Failures
- Business Analysis in an Uncertain EconomyJonathan Babcock
- Why We Lost Focus on Development PracticesAgile Management Blog
- Talking about what we doRequirements Defined - Seilevel's Software Requirements Blog
- BPM is not Software EngineeringGo Flow
- 3 Big CaliberRM Gotchas And How To Fix Them Part 1Requirements Defined - Seilevel's Software Requirements Blog
- Project World and World Congress of Business Analysts (PW&WCBA)Better Projects
- Troubled ProjectsHerding Cats