Month: January 2010
Requirements for Outsourcing
Outsourcing differs from other development because there is bound to be a contractual relationship, probably a geographic distance, a different sense of loyalty, language misunderstandings, cultural differences, reluctance to speak up to the client – and many other associated problems. Good requirements are always a problem, but outsourcing increases the problems, and makes even great […]
Read More
Real Reuse for Requirements
Requirements reuse provides organizations with the unique ability to share a requirement across projects without absorbing unnecessary duplication of artifacts within a repository. This is a critical capability that accelerates time to market and cuts development costs. Shared requirements can either track to the ongoing change made by the author or they can remain static […]
Read More
Business Analysis in Extreme Programming
This article “Business Analysis in Extreme Programming” describes the myths associated with having business analyst between the customers and the development staff. This approach is indicative of agile processes, in which the questions is asked how can we avoid confusion and get closer to the source of information?
Read More
Structuring Use Cases with Goals
Everyone talks about “requirements analysis,” but not much is said about the requirements analyst. What kind of person should do this job? What do analysts really do? What do they need to know?
Read More
Writing Complete User Stories
This blog post discusses how to write complete user stories, dealing with the issues identified by Alister Cockburn with decoupled user stories.
Read More
User Stories and Use Cases
This blog post discusses the differences and commonalities of user stories and use cases, helping you decide when and how you should use them.
Read More