Eric Ries' seminal book The Lean Startup can be applied to many facets of software development. Lean methods aren't just for startups - they're a way to spend less money and effort building the right (and most profitable) thing. Software development is inherently unpredictable, and companies that invest heavily to design and then build a comprehensive software product or service before delivering any of it to customers often lose money. This typically happens because the designed product includes a large number of ideas, and only a small percentage of these turn out to be valuable to users. In some cases, the core theory of it's most valuable feature is a mistake, making the entire product a failure. Eric describes in The Lean Startup approaches he used at his first companies to employ the scientific method to direct the activities teams use to deliver products. He also provides examples of how to do so with minimal investment.
All Content about Lean Startup
When programmers estimate code on software projects and they turn out wrong, who’s to blame?
You can help a company profit more with the software they build by showing them the right things to measure – but expect some resistance on your project…
When talking about the differences between scrum (or kanban) and agile development, the motor and steering wheel of a car can be a useful analogy.
It’s always been popular to tell people how they’re “doing it wrong” and agile software development is just as easy to call “fake”.
Software developers are often frustrated when a product manager changes the design at the last minute. But product managers are a programmer’s best friend!
If you’ve ever been on a software project and wondered: “what’s the impact of the work I’m doing?”, impact mapping will help you immensely.
If you’ve ever thought “who came up with these ideas?”, you probably need a business model canvas on your agile development team.
It takes special software leadership skills to learn what customers want through lean software development.
Why do some companies build products with the freedom of a lean startup, while others deliver boring products like a feature factory run by control freaks?
An agile budget is a major key to healthy software development company culture – and careers! Budgeting is something we don’t pay attention to enough.
Too many companies and agile coaches keep the secret of scrum from people! Without understanding WHY to use scrum – misery often results.
To let the customer take a larger role in deciding what’s in your product, and release it multiple times per day — you’ll have to overcome attachment.
The term “feature factory” coined by John Cutler is an accurate description of what happens when a software team pursues output above all else.
A team that learns from software project failure produces better software – when you plan to exploit this ability.
Whether they realize it or not, many people in software development companies select processes based on their tolerance for uncertainty.
Getting ready to redesign a new version of a software product? Avoid the top 5 software redesign mistakes I see made all too often.
Evolving software architecture to adapt to product growth helps you deliver faster and refactor easier as the project progresses.
A/B software development to find what customers value. Relying on planning up front based on customer feedback and research just isn’t competitive!
Experienced technologists know the variables in software development are nuts, and estimating to account for all possible outcomes doesn’t work.
Avoid the traps many teams who have never delivered a software product in a truly agile fashion encounter when delivering a minimum viable product.
If your team is pursuing agile but it doesn’t feel like it lives up to the industry hype, confusion about agile project management may be the culprit.
Your software team can avoid becoming irrelevant in today’s shifting technology market by investing in and building software differently.