Evolution of Agile world with Lean Startup Concepts
Lean Startup has revolutionized the startup movement. Startup world is looking like more scientific these days. Because of that reason, a flood of people are trying their hands by opening new startups. However is there anything to learn from Lean Startup for enterprises using agile methodologies currently? This session tries to answer the same - ranging from how to use Lean Startup techniques as part of Agile Product Ownership to changing current Agile practices focused towards validated learning and customer development.
Take away for audience from this session is:
- How Agile Product Management can scientifically define, what exactly to build and why?
- How some important Agile practices need to improvise themselves based on Validated Learning and Customer Development concepts of Lean Startup?
- Instead of building the MVP or product features directly and finding out later that customers don't need them, finding that out sometimes without writing even a single line of code or with minimal investment and resources.
Outline/Structure of the Talk
- How a team and product-owner interaction happens in an Agile team (2 min)
- How the same interaction happens in Lean Startup team (5 min)
- Why Lean Startup approach? (5)
- What's Lean Startup? (5)
- Agile + Lean Startup practices (10)
- Definition of Done
- Continuous Deployment
- Innovation Accounting
- Validated Learning
- Agile vs Agile+Lean Startup approach (10)
Not everybody is working in a startup. On the outset it looks like Lean Startup practices are relevant to startups only. However if you take a closer look they are relevant to Agile teams in the same breath.
Agile is a software development process and has nothing to say about whether the business goals are correct or not. If an Agile team receives bad information from upper management, the product will fail in the marketplace. On the other than, The "Lean Startup" model is a business process that complements Agile nicely, but it's not a software-development process, and focus strongly on things like goals.
So even though companies follow Agile, they still fail as they may not be working on the right things for the business.
Lean Startup approach helps a Product Owner in factually define the business value based on validated learning. Sometimes no implementation is required for the validated learning.
This session introduces these concepts to Agile practitioners and explains how they can be useful for a product owner for business success.
Product Owners, Agile Team, Enterpreneurs
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Evan Leybourn - If you need to start a project, you’ve already failed #noprojectsEvan LeybournAuthorDirecting the Agile Organisation
schedule 4 years agoSold Out!
I want to be controversial for a moment and propose an end to IT projects, project management & project managers. I propose that the entire project process is flawed from the start for one simple reason. If you need to run a project, you've already failed.
By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.
This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.
This presentation will introduce you to #noprojects. You will learn how to define an outcome and create an Outcome Profile. You will also learn how to manage change within the context of an outcome through the Activity Canvas.
ShriKant Vashishtha - Specification by Example ExplainedShriKant VashishthaAgile CoachMalonus
schedule 3 years agoSold Out!
What if you could write functional tests without writing a single line of application code? What if those tests are written in plain English (so that anybody could understand) but still it's executable spec or source-code? What if you could generate the documentation from live production source code? Now you don't need to update the requirement doc all the time.
What's Specification by Example? Is it different compared to BDD? Who all participate in defining these specifications? Are functional tests and functional specifications same? These are the questions this session tries to answer.
ShriKant Vashishtha - Completely Distributed Agile - A Case StudyShriKant VashishthaAgile CoachMalonus
schedule 3 years agoSold Out!
What about a case where the whole team is completely distributed, i.e. every team member works from home, possibly from a different country or from a different time-zones. What about the challenges faced by a team where team-members are distributed with 7-8 time-zones.
In the new era of Lean Startup, some startups are working and developing software in this fashion. This session is a case-study of one such startup which is completely distributed. How they are working, are they using Agile or have evolved some new practices which work for them. What kind of different challenges these teams face on regular basis and how do they solve them, these are some of the question this session tries to answer.