Once you have a thorough understanding of the business case and your users, you will need to define what the overall requirements are of the application. How you do this will depend in large part on the development methodology you are using. If you are using the Agile methodology, you will start by defining user stories and prioritizing them. For other methodologies, you will want to create a requirements document that will fully define what you build.
- [Voiceover] In most application…and development methodologies a critical first step…is defining the Feature Requirements.…The way this is done will depend in large part…on the methodology you use.…The key differences are between Agile…and other methodologies.…If you're using Agile or Scrum,…you'll begin by creating User Stories.…These are descriptive elements in the format of:…As a type of user,…I want a feature so that some reason.…
For example: as a food service subscriber,…I want to be able to add a food product to my order…so that it can arrive with my meals for the following week.…This allows the developer to see the main information…and purpose for a feature.…Note that there are ways to add additional information…if necessary to these user's stories.…Then we prioritize these features using the business case…and user information to group them…into the MoSCoW priorities.…This is Must have, Should have,…Could have, and Won't have.…
Or you can use something else similar.…As we work on each Sprint,…we'll drag these items into In Progress…
Author
Drew Falkman
Released
2/1/2017- Hiring a great team
- Outsourcing
- Enhancing team communications
- Creating a product roadmap
- Capturing and using data and analytics
- Identifying key performance indicators
- Choosing which platform to use
- Managing the product life cycle (PLC)
- Taking feedback
- Public speaking
- Running efficient meetings
- Marketing and launching products
- Growing and scaling
- Managing crises
Skill Level Intermediate
Duration
Views
-
Introduction
-
Welcome1m 36s
-
What you should know1m 16s
-
-
1. Your Team
-
Being CTO is a people job1m 57s
-
Hiring a great team6m 28s
-
Outsourcing5m 29s
-
The importance of flow4m 40s
-
-
2. Product Management
-
Your job is the product1m 59s
-
Creating a product roadmap3m 52s
-
A/B and multivariate testing2m 45s
-
-
3. Technology
-
The great platform choice5m 27s
-
Hosting and servers3m 54s
-
R&D for you and your team3m 55s
-
-
4. Development and the Product Life Cycle
-
The product life cycle4m 15s
-
Defining the requirements2m 23s
-
The design process4m 7s
-
The prototype process3m 8s
-
How to take feedback3m 19s
-
Minimum viable product3m 6s
-
-
5. Marketing and Communication
-
Public speaking3m 38s
-
Running efficient meetings3m 13s
-
-
6. Business and Entrepreneurship
-
Being proactive4m 14s
-
Managing up3m 26s
-
P/L and business numbers5m 50s
-
Growing and scaling5m 30s
-
Managing crises2m 33s
-
Conclusion
-
Next steps40s
-
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Defining the requirements