Why we got rid of SCRUM to become agile again
Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles. After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time. We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best part from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization
Outline/structure of the Session
We adopted agile and scrum in our organization over 4 years ago. While it had great initial benefits and allowed us to truly embrace the spirit of agile at the beginning, it has become stale and people have started forgetting why we did it in the first place. Agile and specifically scrum fatigue started to set in. The teams became too focused with the scrum ceremonies and started losing sight of the true meaning of agile. In this talk I will go over several scenarios we experienced in our day to day that clearly went against the agile philosophy and mindset and what we had to do in order to get the agile mindset back. The session will have the following format:
Introduction - Discuss the challenges facing us when I joined the company and and some of the steps we took in order to get us working better and creating a great software product.
The Challenge - Discuss the challenges we faced as we kept growing in a pretty rapid pace
The Solution - Once we realized that the process was no longer working for us, we had to get together as a team and really evaluate our process. We did a department wide full day retrospective session in order to isolate our biggest perceived issues and come up with a plan to address some of them.
Conclusion - Where we are today
Attendees of this session will:
- Learn what worked for us and what didn’t in hopes of implementing or changing their own process
- Be encouraged to evaluate their process and ask questions. Determine if what they do works and helps their team members and end users
- Be exposed to different types of agile processes in order to help them understand what may work for them in their organization
scrum masters, managers, developers
schedule Submitted 3 weeks ago
People who liked this proposal, also liked:
Lisa Fast - Not too minimal: UX research in a Government MVPLisa FastUX UnicornVation Inc.
schedule 4 days agoSold Out!
Lean UX research is essential to guide and validate what exactly is the 'Minimum Viable' to launch a Minimum Viable Product, especially in government.
In this talk, I'll describe how user research insights helped us understand, design and launch Canada's first online open-source regulatory consultation. The first research participant identified a significant hole in our assumptions - and predicted that we could miss the minimum viable mark. It helped us course-correct, and plan ahead for the next development iteration.
The other customer group was the government. We applied lean UX research techniques to understand the government analyst team's journey and needs, and then to co-design with them as the analysis site MVP was developed, and as the commenter data flowed in.
I'll describe how the insights from the research helped us meet the Minimum Viable mark for the government customers, understand how and why we missed the mark with the specialist customers and how you can apply lean UX research techniques to ensure you don't iterate your way to a useless product.
Ken McMillan, PMP, CISSP, ITIL, MIPIS, PCIP - That's nice and you're nice ‒ but I don't care: Aligning service-delivery to business requirements in the public sectorKen McMillan, PMP, CISSP, ITIL, MIPIS, PCIPSenior AdvisorOffice of Small and Medium Enterprises, Public Services and Procurement Canada
schedule 3 weeks agoSold Out!
In the federal public service there is an almost-complete disconnection between the performance evaluation criteria applied to business leaders and the criteria applied to service providers.
As a consequence, even in situations where both the business and the service provider enjoy optimal relationships, the goals are not the same and may even be entirely contradictory.
In a climate centered on Results and Delivery, leaders cannot expect results if they do not mitigate this conflict.
The approaches proposed in this discussion align the service organization to the business. They promote mutual accountability by insisting on mutual performance alignment between the business and its services provider.
Steve Lavigne - Going Vertical; A Value Driven Approach to Web DevelopmentSteve LavigneProduct OwnerOPIN Software Inc.
schedule 1 month agoSold Out!
One of the biggest development hurdles we face when new to any agile framework is switching from a ‘phased’ approach to a ‘vertical slice’ approach. Individuals and teams often aren’t used to deconstructing projects and problems in this way and we often hear “what about the dependancies” or “the system is too complex”.
In order to speed up feedback loops and provide instant value to clients, we can take a large feature and break it up into several small pieces that slice through each of the systems architectural layers. We can break down almost any of the features we do within projects into slices that take a couple of days, at most, to get out the door. Each slice is comprised of any work needed to be done in a system architectural layer, as well as, any testing that may need to be done to make it ready for deployment.