This article looks to discuss ‘Project Outputs and Deliverables’. It provides an introduction to the project outputs and deliverables starting with where it all starts and the initial project idea.
Project Outputs and Deliverables
A 59 Seconds Agile Training Video
Project Outputs and Deliverables For Product Owners
A 59 Seconds Agile Article
Successful product delivery depends on meeting the customer’s expectations; bug-free code should be part of the package, but the first prize for the customer is what they asked for in the first place.
Project Outputs and Deliverables: Where it all Starts
So how do we get the expected results? We need to apply the principles of new product development (NPD) in general, and then use a few specifics from Lean Startup theory. This starts with the idea for the new or improved product. This could be a simple “lightbulb” idea from one of the executives, or the output from a brainstorming workshop. In many organizations, this is enough to get the ball rolling, which is why there are so many product failures and a huge waste of money.
Project Outputs and Deliverables: Getting Shot down in Flames
Before taking the product idea forward, it needs to be kicked around and tested for viability. Many of the criteria are financial, such as what return on investment (ROI) will there be and when, and what the CAPEX costs will be. The really important questions are about the target market for the product. There is a succinct saying “there is a gap in the market, but is there a market in the gap?”. As this is being written, there are mobile app developments being churned out that very few customers will bother to download: a case in point is an app that reminds you to renew an annual subscription (and there are plenty of them).
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
If the product idea was formulated in an innovation workshop, hopefully, they have also completed the viability checks. If the idea does not pass the criteria for success, it should be shelved right now. This does not mean it cannot be re-examined later; maybe current technology is just too primitive or expensive now; think of the special effects available to George Lucas for Star Wars in the 1970s.
Continue Reading —> Next
The Agile User Stories and Tasks
A 59 Seconds Agile Video Animation
Continue Reading —> Next
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.