Year: 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 MoreWhat 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 MoreUsing 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 MoreStop 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 MoreRequirements Gathering with Mind Maps
Although the actual scale of the issue is arguable, it’s well established in the Project Management community that a very significant proportion of failed projects are due to poor requirements gathering in the early stages of defining project. There are many approaches, and no magic solutions, but this video shows how to use a Mind […]
Read More