Month: May 2013
Agile Requirements by Example
System-building projects which fail (which is many of them) do so more often because they build the wrong thing, not because they do a bad job of building the right thing. The Agile community has developed a range of techniques for making sense of system requirements and capturing them in artifacts that are familiar and […]
Read More
What Makes a Good Product Owner?
This short video discusses what makes a good Product Owner in a Scrum Agile team, how to engage your Product Owner and some pitfalls that can come with the role.
Read More
Using UML or IDEF for Business Modeling
The Unified Modeling Language (UML) is a modeling language standardized by the Object Management Group (OMG) used to manage requirements in software development projects. IDEF, the acronym for Integration DEFinition, refers to a family of modeling languages in the field of systems and software engineering.
Read More
Describe User Interaction with Scenarios and Storyboards
A user story is a tool to describe the product functionality, but it is less useful suited to describe in detail the user interaction. Agile scenarios and storyboards are tools you need to describe the interaction steps. In his post, Roman Pichler what scenarios and storyboards are, how they can be used effectively in an […]
Read More
Stop Building The Wrong Product Righter Build The Right Product
Learn how to build outcomes over outputs as a key strategy to building great products using the Target Outcome framework. The talk will cover why the metrics we often use are flawed, how to create useful value metrics, track value incrementally and do guerilla user testing.
Read More