All Entries Tagged With: "pitfalls"

What’s in a Signature?

Is there such thing as a peaceful, amicable “sign-off”?

Patterns and the Evolving Business Analyst

Let’s focus on what I consider the capstone to development and “evolution” as an analyst; the ability to learn, recognize and apply patterns.

A Few Quick Links – 12/18/08

New idea for requirements collaboration, lots of project management terms, more evidence on the link between poor requirements and project failure, and, for Heaven’s sake, we don’t “gather” requirements!

Agility vs. Bureacracy (and other thoughts)

How long will “Agile” remain agile?

Business Analysts and the Abilene Paradox

You don’t agree at all with a decision, but you fear that you may be the only one – in disagreement. So…

More Analysis Paralysis

Breaking out of analysis paralysis doesn’t require you to lower your standards, or to aim lower than you would otherwise. It just requires some prioritization. What you have to do is identify those things you have to get right from the get-go, those items that do need analysis, and what can be fixed later.

Curing Analysis Paralysis

You’ve poured your heart and soul into drafting the perfect requirements specification. You’ve checked, doubled checked, and triple checked every syllable of the document for clarity, spelling, testability. You have full traceability to every business requirement. You’ve been extra, extra careful not to tread in the domain of design. Your spec is rock solid.

So, why, after 5 review sessions with project stakeholders and document consumers, are you still making edits?

“Party of Four” Key Considerations in Product Development

This “party of four” key considerations comes from Adam Bullied at writethatdown.com. Basic? Absolutely. Product management 101 type stuff? Yes, sir. But if you’re not including these 4 key and simple concepts in your product planning you probably ought to.