“Agile … is an attitude, not a technique with boundaries. An attitude has no boundaries, so...Read More
My personal study of what makes successful teams, to which I’ve recently alluded, is ongoing. Most recently I came across the article “Project teams are not teams”, which seems to provide a pretty direct answer to the question I posit in the title of this post.Read More
Here are just a few impressions I’ve jotted down over the past few weeks that may never evolve into full blog posts, but that I wanted to share just the same. Please feel free to chime in with your support or challenges to my list, or with your own observances.Read More
This post is spurred by a few articles I’ve read recently which have only served to reinforce some similar thoughts I’ve been having for a while now on the constant, competitively toned comparisons between agile and traditional development methodologies.
As I read article after article extolling the wonders of these new methodologies against the weaknesses of the traditional methods, I begin to wonder if the emphasis isn’t too much on agile methodologies over agile principles.Read More
There have been some really interesting articles in recent days and weeks that have been comparing use cases and user stories, and highlighting the advantages of each. I’ve cherry-picked some of the best from my collection of bookmarks to share with you here.
Regardless of what method you use, it is good to be familiar with the available options and their relative strengths and weaknesses.Read More
We don’t use SCRUM or XP in my shop, but I am always interested in learning more about other methods and tools, and I know some of my readers use these methodologies, so I thought I’d share some information on Sprintometer, a free SCRUM & XP project tracking tool.Read More
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