What should you Build Next?
bug/feature/refactor
A feature is a new capability to the software
You add features when your software can’t handle some users use case
Improvement: improvements are interactions to make an existing feature better. It can make the feature easier to use. It can make the feature faster to use.
Bug: a bug happens when a feature is implemented and not tested properly, or when some edge cases were not considered.
Refactor: it is when we improve the code structure without changing their behavior
First principles first
Instead of build a new feature for each user wish, try to understand the core problem they have in their workflows.
Prefer build low level building blocks features that can be reused in many workflows
Try to solve a set of problems instead just one use case.
Prefer a more generic/extensible feature than a much more specific
Do not build for a single user, build for a group of them
Basecamp Shape Up
Principles of Product Development Flow
You should decide on what to work on based on the cost of delaying it.
How is the cost of delaying fixing this bugs?
How many users are affected by this bug?
Is this bug generating inconsistent data?
Is this bug part of core user workflows?
Can user use the product even with this bug?
How many customer supports ticket will be open because of this bug?
How is the cost of delaying this refactor?
How many more hours developers Will spend before this refactor?
How long will take this refactor?
How this refactor affects the other devs?
What is the risks of this refactor?
Can this refactor be done incrementally?
How is the cost of delaying this improvement?
How many users will perceive this improvement?
How this improvement will affect users?
How many users uses the feature that wil be improved?
How is the cost of delaying this feature?
How many users are waiting this feature?
How this feature helps sales team to sale more?
Is this feature for any user or high usage users?
Will this feature improve usage and engagement?
- The Nonesuch BeastNon-coders will provide many requirements that are simple by itself, but in combination they can't exist. Instead of trying to solve all the problems with specific features We…
- Principles of Product Development FlowThis book is about techniques to improve your product development flow In manufacturing you generate value creating the same product In product development you only generate value…
- The Nonesuch BeastNon-coders will provide many requirements that are simple by itself, but in combination they can't exist. Instead of trying to solve all the problems with specific features We…
- MVPMinimum Viable Product needs to deliver value to the user. It should feels a Gap of user needs. MVP does not have all the features the users wants, but it has/solves to core user…
- Product Development3 buckets a gamechanger: people buy because of this feature a showstopper: people won't buy without it, but adding it won't generate demand a distraction: feature with no value…
- AudienceAn audience is a group of people that is listen to a talk, that will use a product. In the same way a talk can fail when targeting a wrong audience (A Failed Talk A…
- ChangeMost people only change when a change happen to them Big companies (winners) only moves when something changes Startups should change/adapt before the change come Links
- Creating, Improving, RemovingMost organizations only value creating new things (features) You also create value when you improve the efficienty of current systems And also when you remove complexity and bad…
Sign in with GitHub to reply.
Select any passage to quote it.
Comments