Stakeholder interviews, necessity of the functional spec - or not, document templates, non-functional requirements and more.

Ok, time for something light. This is funny stuff. Forget the phases or iterations - THIS is how the development lifecycle really plays out… Right?

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.

E-mail is a great communication medium, but it is not without its weaknesses.

E-mail is the most widely used Internet application. There’s a fair chance that you don’t know anyone between the ages of 15 and 65 that doesn’t have and use an e-mail address. For all of it’s popularity, e-mail is often used ineffectively.

This post is the first of a small series of writings on effective use of e-mail in a business environment.

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?

If you’re new to use case modelling, or just need a refresher, here is an excellent resource; the UML Use Case Diagrams: Tips and FAQ.