My employer, Jabian Consulting, produces a semi-annual publication of our consultants’ latest thinking on today’s most important business and technology issues. The Spring, 2014 issue just came out today, and it’s really good (and I’d say that even if I didn’t work there!)! You [...]
Occasionally, an analyst will encounter a stakeholder who wants to prescribe the detailed solution on day one. What then? Here are a couple techniques that have served me well over the years.
The model that really matters is the one that people have in their minds. All other models and documentation exist only to get the right model into the right mind at the right time.
If we can learn those basic, timeless principles that make any project successful, we’ll be able to identify them and adapt more easily to any environment whether waterfall, spiral, scrum, or the next big thing. One of those principles is that of enabling and empowering the cross-functional team.
So, what exactly are small wins, and why do they seem to add up as well as they do? As solutions professionals, we are ideally suited to make a difference when we help our businesses make those incremental changes which, over time, add up to significant wins and success in the marketplace. This post will include citations from sources I’ve come across while studying the topic of small wins on my own.
Agile team members must know something about teamwork and this means understanding a lot about human behavior and why people do the things they do!
Just a brief quote and a comment this evening to capture a thought that crossed my mind while contemplating the main differentiators between the great analyst and the good.
standard Requirements Documentation Tip: Distinguishing between Business Rules and Software Requirements
Many BAs I coach make the mistake of mixing software capabilities with business rules, employee procedures, and operational guidelines when documenting requirements for an information system or software application.
Think of requirements as inventory or as component materials in a storage bin with a shelf life and a carrying cost. Inventory isn’t free. You have to pay someone to produce (model and document) requirements. You need a supply of good, current (fresh) requirements to produce a quality product.