Let's experiment is obviously a better strategy than "It's too complex"
Software projects are notoriously complex making them hard to successfully manage. Or are they?
In this talk I will demonstrate, through the Cynefin framework of Complex Adaptive Systems, what makes projects complex, what common strategies lead them to failure, and how to increase early and frequent decision making that promotes either an early termination of a failing project, or a successful ending.
Outline/structure of the Session
During this talk I will present the Cynefin Framework using real-life examples of software projects, and ample relevant metaphors.
1. Project planning styles
2. Predicted vs. empirical planning
3. Feedback loops
4. The Cynegfin framework
5. Empirical planning and visibility tools
6. (Time permitting) ongoing planning using a Kanban board
This talk is based on a session presented at the Israeli Ministry of Education conference for superintendents
- Introductin to Complex Adaptive Systems
- Introduction to empirical planning and common tools
Managers, Scrum Masters, Lean Mentors, Team Leads, PMOs, Anyone wishing to lead an agile transition
schedule Submitted 2 years ago
People who liked this proposal, also liked:
The New Agile
We know that agile methodologies work at the team level, and there is now even an effort to scale into whole organizations.
There is a clear reason behind this: we found ways to improve performance, by analyzing situations better, and making better decision. Every organization wants to apply this in every level. Like in the late 90s, new ideas are coming out that challenge the way we think, and this time they don't just answer development. Ideas like Beyond Budgeting, Lean Startup, Cynefin, Real Options, Feature Injection, SAFe, Design Thinking, #NoEstimates, Cost of Delay and others are spreading out, and while we know not all will last, you never know which might fit your situation.
In this session, I'll give a summary of what's hot around the agile world, with some criticism and application in the real world. 14 years after the original manifesto, organizations start to experiment again. I always wished I was there when the first conversations took place. I encourage you to join in on current conversations. Let's start.
You’re in that zen mode, ready to go into designing code with tests. You know all about emerging design, your mind is empty, and off you go.
What scenario do you pick to start with? How do you translate not-so-specific requirements into example tests? What happens when you run out of examples? Do you ever get back to the first requirement, or skip between tests as more bright ideas flash into your mind?
Over the years, I’ve discovered patterns I use in TDD. From improving names, mutating tests to create more examples, picking scenarios and differentiating them from their siblings. I’ve noticed others doing them too.
In this session, I’m going to tell you about my experience, and what methods are effective for me. I’m going to show examples, explain the thought process, and tricks that help me along the way.
ROI is Dead
We’ve always been told that because anything has both cost and value, we should make decisions based on Return On Investment.
The problem is that nobody told us that it’s just plain stupid.
ROI as a decision mechanism doesn’t work. It is possible to get the cost part right (maybe), but the value cannot be measured. We don’t know when to measure and even how. And because of the complex world we live in, the success of our next product depends on the one we’re working on now. Frankly we don’t know the impact of our current investment.
Take testing for example: How do you measure value? Bugs caught before release? General customer impression a year from now? We can put a number on the investment, but not on the return.
At this talk, I’m going to make the controversial claim that ROI can no longer be used as a planning tool. Organizations using it are risk-averse, deciding based on costs, rather than opportunity.
Join me and the modern world, and leave the metrics of old behind!
The evolution of Customer satisfactionElad Sofer
schedule 2 years agoSold Out!
"Our highest priority is to satisfy the customer..." Says the agile manifesto. But how do we achieve customer satisfaction?
This topic has been bothering many people and organizations over the years and we have witnessed several approaches and practices to try and reach this Holy Grail.
During this session I will review the evolution of customer satisfaction, starting at the dawn of history and ending with the tools and practices of today.
I will review the tools being used by today's successful organizations and will provide some tips and advice on making sure your customers are happy.