We previously stressed the importance of understanding why something is a requirement. Unfortunately, we can’t just ask “why why why?!” until we reach the end of the chain. This won’t be any more effective for us now than it was when we were in kindergarden. Eventually, our listeners will get frustrated, or worse, defensive.
Communication / Consulting / Lists / Requirements / Requirements gathering / Software development / Software requirements specification
Posted on:
Top Five Requirements Gathering Tips
Interviewing, Brainstorming, Documenting Use Cases, Prototyping, and Analyzing Documents are our top-five tips. Read more for details
Polls / Requirements / Software development / Test Automation / Testing
Posted on:
Software Testing Series: Black Box vs White Box Testing
Should I use black box testing or white box testing for my software?
You will hear three answers to this question – black, white, and gray. We recently published a foundation series post on black box and white box testing – which serves as a good background document. We also mention greybox (or gray box) testing as a layered approach to combining both disciplines.
Given those definitions, let’s look at the pros and cons of each style of testing.
Communication / Consulting / Requirements / Software requirements specification / Writing
Posted on:
Are people reading your requirements? A blogversation.
Tony just put up a post at Seilevel’s blog on making sure your spec is reviewed. Kent Newsome recently posted about starting cross-blog conversations here, possibly inspired by Amy Gahran’s post about it here. Tony’s post is a great topic to cross-blog about. Three easy steps to blogversation Post your […]
Process Improvement / Requirements / Software development
Posted on:
More on choosing the right software process
B. Scott Burkett writes a post, Choosing the right methodology, that is worth a read. He proposes that you pick your process (incremental, RUP, agile, waterfall) depending on the circumstances of each project. This builds nicely on the discussion we started in our Foundation series post, Software process (waterfall process […]
Process Improvement / Requirements / ROI / Software development
Posted on:
The Best Way to Improve ROI is With Good Requirements
Statistics that support the critical need for requirements management improvements…
Foundation series / Process Improvement / Requirements / Software development
Posted on:
Foundation Series: Structured Requirements
Karl Wiegers wrote the book on structured requirements – Software Requirements, 2nd Edition, Karl E. Wiegers. If you are involved in managing requirements, you should own this book. Even if you don’t follow his approach to managing requirements, or don’t like how he deals with use cases, you should still […]
Austin TX / IEEE / Organizations / Requirements
Posted on:
IEEE Austin Event: Seilevel presents on requirements
Jerry Aubin and Joe Shideler of Seilevel will be giving their presentation, Beyond the System Shall – A Journey from Good to Great Requirements. Although this meeting is sponsored by the Austin chapter of IEEE, it is open to the public. [Update: The meeting is from 6:30-9:00pm on Wednesday 15 […]
Foundation series / Process Improvement / Requirements / Software development
Posted on:
Foundation Series: Software Process (Waterfall Process versus Incremental Process)
A software process is the set of activities required to create software. This process can be defined with very precise steps, roles and responsibilities. The process can also be defined with a more fluid set activities in pursuit of concrete, high level objectives. Or software can be created without explicitly […]