Trio of trouble: how design thinking, lean and agile work together
Which way is right? They all are. This talk untangles what these movements, mindsets, and approaches mean, and helps teams and leaders to choose the right bits at the right times, and bring it all together into one big happy collaboration.
The way we do product development constantly evolves and every few years, there’s a new wave of thinking that promises to be the secret key to doing it better. The 90’s saw the rise of the Agile movement for building software better. A bit later, the lean mindset shifted the focus to value creation for the entire organisation. More recently, Design Thinking has democratised design and brought it to the boardroom.That’s awesome! But it leaves leaders bamboozled by an unprecedented array of frameworks, methods and approaches – paralysing meaningful progress. Boots-on-ground practitioners are also confused about how to work with their colleagues from other camps too.
Can these approaches work together? How do we know if we’re doing it right? How does it all fit together? Could this work in my organisation?
This talk will help you find answers to your questions, bringing clarity to the topic, and some practical guidelines to help you find a way that works for you.
Outline/structure of the Session
0-5: Introduction and framing
- Tell a relatable story that illustrates the frustrations and challenges that teams face when considering these approaches
5-12: Ten-thousand-foot summary of each approach, covering:
- Origins (extremely brief potted history, told through anecdotes)
- Purpose, principles and mindset
- Overlaps, similarities and differences
12-22: Theory in practice
- Applying the different mindsets to aspects of software/product development
- Choosing the right methods and tools
- Success factors for working with other teams
22-35: Guidelines and anti-patterns
- 5-7 takeaway guidelines
- Common anti-patterns, showing what not to do, illustrated by real project experiences
35-40: Wrap-up and Q&A
A few notes on how I present stuff.
I'm not a conference circuit speaker, but over a few years of learning what works, here's a few things I strive for:
- Make it not about me. Nobody learns anything when people just talk about themselves. And it's boring.
- Make sense of stuff, and communicate it as simply and briefly as possible, using everyday language. Especially anything that's background or theory.
- Illustrate key points with real experiences. Have a story that supports why I believe what I believe.
- Be vulnerable - talk about when things haven't worked, and what was learned. Hands-down, this is what people say was the best part when I talk with folks afterward.
- Don't preach one universal framework, process or method. Nothing is ever that simple. Instead, help people ask better questions and find their own answers.
And finally, this talk has not been presented before - or written yet! - but it is based on an report for O'Reilly Media that is being written now, and scheduled for publishing in June 2017.
- The meaning, mindset and mechanics of Design Thinking, Lean and Agile
- When to use each approach, and where they overlap and intersect
- How to combine the right mindset with the right tools at the right time, to rise above rote application of methods
- Guidelines for getting started and working with other teams
- What not to do, from lessons learned in the trenches
Product managers, designers, developers - anyone involved in building software!
schedule Submitted 1 month ago
People who liked this proposal, also liked:
How a Large Business Sprints Like an Agile StartupBrad Bennett
schedule 1 month agoSold Out!
Don't Look Back in Anger: Wildman Whitehouse and the Great Failure of 1858Lilly Ryan
schedule 2 months agoSold Out!
In the 1850s, Edward Orange Wildman Whitehouse was appointed the lead engineer of the first attempt to build a trans-Atlantic telegraph cable. With the entire population of two continents waiting for his go-live, their handlebar moustaches aquiver, he demonstrated in fine form just how spectacularly a big project can be a bigger disaster.
This is a tale of long-winded rants, spectacular sideburns, and gentlemen scientists behaving badly. It is also a lesson about the importance of honest reflection in technical teamwork. Lilly outlines some of the mistakes made during one of the biggest tech delivery projects in history, and how a constructive view of failure helped to turn it all around. Through the public meltdowns of Wildman Whitehouse you will learn the importance of feedback, how to handle complex tasks gracefully, and the best way to recover from having your pipeline eaten by a whale.
Survival guide for women in ITAnna Fiofilova
schedule 2 months agoSold Out!
BeginnerWorking in the IT industry today is hard, but it is even harder if you are a woman. There is still lots of “old school thinking" that women face daily. This talk is a survival guide based on real-life stories and different challenges from women of different ages, cultural backgrounds and roles in the Australian IT industry.Like any survival guide, this one provides you with the essential information to help you identify and overcome the most frequently encountered hazards. Each chapter contains useful tips, instructions and practical advice on a particular issue so you can implement the skills and techniques even under the most stressful circumstances. From the hiring process to promotions and corporate events, you'll have the tools to survive.You will learn these skills and more:
Preparation is the key. If you are starting your career in IT or navigating through it - this guide is for you.
- Assess your situation and prioritize your needs;
- Surviving techniques for the hiring process;
- Assemble your own custom emergency kit with essentials tools;
- Manage extreme work conditions and overtime;
- Survive corporate parties and drinks;
- Build trust network and create allies;
- Identify your enemies and their habits.
"How do I test this?" - Exploring test plan design
In this interactive session, Rob and Many from REA Group will go through an exercise designed to explore the agile testing mindset. Together with the rest of the room we will build up a mindmap of a test plan for a simple application.
Testing is an often mis-understood, under-estimated role. We hope to challenge people into thinking outside the box and give people a better understanding of what a "QA" role brings to a high performing agile team.
The hallmarks of successful teamsMiles Jordan
schedule 2 months agoSold Out!
What makes a team successful? What makes the work that they do so valuable, useful and delightful?
In this talk, we'll look at some of the research that's analysed successful projects and teams, as well as draw on some of my own experiences in running delivery teams. While targeted towards product delivery teams, most of the concepts can be applied to just about any team.
When we're done, your team will be happier, healthier, more efficient, and your customers will love you for it.
Learn to Play; Play to Learn!
Games are fun! We use them from childhood through to corporate events; and we often don’t realise that we’re learning at the time. We cover how games continue in that vein; in helping individuals and teams in so many ways. Games can help solve team problems, re-engage teams, build trust and understanding, and much more.
We work through scenarios where games have been employed to achieve varying outcomes; including why games make sense (at the right time); and how games help people get the point, while laughing!
In short, playing games costs little, adds significant value and can have amazing results!