We have a culture here that we do the use cases first and then work on implementation and then derive the requirements from the use cases when all is done.
But I learnt that the requirements always have to come first, so that we are always reminded of what we are trying to solve while doing use cases.
How do you do it?
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
Which will give you a MVP
Cut down on the original reqs to see if MVP is worth the scope ( to launch sooner)
Use cases will be covered in reqs, if not, the requirement collected were not done right
Corner cases next(if needed)
Prototype it
Dog fooding next
Soaking, iterating and optimizing next.
Good luck
What’s important is to identify your target customer segment and hence customer persona clearly.