The Agile Extension to the BABOK® Guide is well worth the read, and I’d encourage any business analyst heading into an Agile project to take the time to give it
Kano analysis, named for Professor Noriaki Kano, is helpful for figuring out what features will have the greatest sway on customer satisfaction. The approach uses five categories for considering satisfaction:
One concept you’ll hear tossed about in an Agile discussion is that of “just enough.” You want just enough documentation, just enough development and testing, just enough time for meetings,
When a company decides, for whatever reason, that Agile is the right idea for them and they are going to go all out to switch over to Scrum as a
The Agile Manifesto is based on twelve principles (I’ve highlighted a couple – 2 and 12 – that are of the most interest for this post): Customer satisfaction by rapid
I’ve seen a number of projects that follow a path something like this — gather requirements (there are a bunch of steps in here), do some pruning, flesh out requirements,
I’ve been fortunate to have been involved in Agile and Scrum with a variety of teams in several different companies. It’s been interesting to see how Agile is adapted to
Don’t miss out on this opportunity
and request a conversation today!
