A picture is worth a thousand words. A prototype is worth a thousand lines of code. Two key elements of product management – and of agile development are elicitation and feedback. Low fidelity artifacts can significantly improve both. Polished, codified prototypes can create problems that prevent you from getting the […]
Agile / Product Management / Software development
Posted on:
ProductCamp Austin Winter 2009
The second productcamp for Austin is just around the corner! Are you going to be there? You should.
Agile / Agile Project: Ratings / Product Management / Requirements / Requirements gathering / Requirements Models / Software development / Software requirements specification / UML Modeling / Use Cases
Posted on:
APR: Mixing It Up With Design And Requirements
With a definition of the important use cases for our agile project, we can move to the logical next step – which is what exactly? Prototyping.
Requirements / Requirements gathering / Software development
Posted on:
Prototype Fidelity
Prototyping is invaluable for getting feedback on a design. It is also great for getting validation of requirements. It can even be used as a means to document the requirements. What level of fidelity should be used when getting feedback? Jan Miksovsky provides some guidance from the real world.
Agile / Process Improvement / ROI / Software development
Posted on:
Two big benefits of incremental delivery
Tarun Upadhyay wrote a fair criticism of our previous post on why incremental delivery is good on his blog today. It is great that he is extending the conversation, and he makes some valid points. We definitely missed a big benefit of incremental delivery, and will cover it in this post.
Communication / Process Improvement / Requirements / ROI / Software development / Software requirements specification
Posted on:
Software Requirements Specification Iteration and Prototyping
Developing great software requirements demands iteration
In our previous post of an example of the software development process, we showed a linear flow through the process, as depicted in several posts over a couple weeks. What we failed to show was any of the iteration cycles, as Deepak points out by asking a great question in the comments on that post. In this post, we will show a little more about how the process works by showing how iteration fits into the machinery of software development.
Austin TX / Process Improvement / Requirements / Requirements management software / Software development / Software requirements specification / UX
Posted on:
iRise – software prototyping tool
We received a comment from Tom Humbarger at iRise on an earlier post, which led us to take a look at their site. iRise provides a tool for rapid prototyping of web-based applications, and there’s an overview of the products available. They have iRise Studio which allows people to create […]
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