Beyond User Stories : Take Your Team to Next Level of Awesome!!!Kalpesh Shah
schedule 9 months agoSold Out!
Great teams make great products, but what fuels this greatness? It's the common understanding and passion for the product but more importantly the singularity of purpose and the feedback loop and how the users are responding to the teams work.
The new world of product development is no longer about scope management and delivering the project on time and within budget but it's now more about hypothesis validation and learning from the users and their behaviors.
The dynamics of product development is changing. As more and more organizations are moving towards maturing their agile software development approach the traditional barriers of roles are being broken creating new opportunities and fostering a shift in the mindset. Instead of being tied down to scope management and delivering the project on time, Agile teams are focused and inspired by hypothesis validation and learning from the users and their behaviors.
In this case study we will go over how a portfolio of 12 SCRUM Teams adopted a more outcome approach and how they shifted their mindset from project delivery in Agile way to adopting the Experiment-Measure-Learn-Repeat loop which plays a crucial role in teams overall motivation, performance and moved from being SCRUM Teams to "Product Teams".
We will also see how we experimented with different team formats and how exposing the team members to different events and user research changed the way they perceived the information of the problem they were solving via features and user stories.
Outcomes-Focused Agility - Story Mapping for achieving Strategic Intent
Florence Nightingale is considered the founder of modern nursing. Put in charge of nursing British and allied soldiers in Turkey during the Crimean War, Nightingale was the first person to define planned consequences from activity as the basis for action when she introduced evidence-based outcome indicators to nursing and healthcare.
Nightingale’s approach was later applied to outcomes-based education and in programme management with the introduction of ‘logic models’. Fundamentally, it is a quality management approach focused on helping us get the desired results from our interventions and activities. Nightingale was arguably the first person who figured out that you need to start with framing the result you want to achieve (the why) to determine what you should do, how you should do it, when you should it, and where you should do it - all the while using an inspect and adapt mindset to interpret actual results against expected ones to determine the next course of action to be taken, including re-framing the expected results based on what we have learned so far.
In this interactive session the two Larry's (Cooper and Sullivan) will be your guides as you learn how to identify the goals and objectives (the why) for a real world scenario, how to use a simple canvas and mapping technique to figure out what needs to be done and in what order, and how to adapt what gets done next based on what we have learned so far. The mapping technique is similar to story mapping except that it provides a deeper understanding of the true nature of most projects in enterprise settings - this technique helps us story-map our strategic intent.
It helps us to more clearly identify and solve the minimum viable problem.
For Product Owners it will help them gain better insights into how value gets defined at an enterprise level and provides a line of sight from strategic goals and objectives down to actual products too be built. For leaders it helps them understand that most projects are often really multiple ones that need to be sequenced and that it is the work that is often not identified and hence not done that sinks most large efforts.
These techniques provide clarity and allow us to deal with uncertainty when dealing with complex problems and messes while maintaining agility throughout.
How Agile is leading the Digital Government Revolution
Governments have typically been slow in adopting Agile principles. In 2014, the launch of the healthcare.gov product was generally considered a failure. At the same time, the Organisation for Economic Co-operation and Development (OECD) published a report recommending governments to implement Digital Government Strategies to bring them closer to citizens and businesses. Since then, the flurry of activities around Digital Government has accelerated and led to some very interesting organizations and initiatives such as:
- UK's Digital Government Services
- The launch of the US Digital Services Playbook
- The creation and growth of 18F
- The creation of the Australian Digital Transformation Office
- E-Estonia's rise to the top of the Digital Government charts
- The creation of the Ontario Digital Government Action Plan and the recruitment of a Chief Digital Officer
Agile methodologies - combined with user-centred design principles - are often at the heart of these Digital Government initiatives. The timing has never been better to help governments accelerate the implementation of Agile principles, user-centred design and outcomes management to deliver better value quicker to citizens.
Through this session, attendees will:
- Better understand governmental constraints and why governments have typically been slow adopters of Agile principles
- Learn about recent worldwide Digital Government trends and initiatives
- Review approaches as to how agile methodologies can be applied in the context of existing Government of Canada IT project management frameworks
- Discuss examples of Government Agile projects and products that have delivered better value quicker to citizens
A Federal Government Shared Service Success Story: Buyandsell.gc.caKen McMillan, PMP, CISSP, ITIL, MIPIS, PCIP
schedule 8 months agoSold Out!
Phoenix, the federal government’s pay modernization initiative, aptly illustrates the federal government’s challenges with successfully deploying shared services. Phoenix, Shared Travel Services, and the Government of Canada Marketplace demonstrate that traditional waterfall project management coupled with an excessive emphasis on specifications can exacerbate risk and produce less-than-ideal results.
On schedule and on budget, Buyandsell.gc.ca began hosting the Government Electronic Tendering Services on June 1 2013. The shared services offered on Buyandsell.gc.ca help more than 80,000 private sector suppliers and buyers representing more than 90 federal departments and agencies to focus on doing business, instead of figuring out how to do business. Buyandsell.gc.ca hosts more than 1 million page views per month.
Buyandsell.gc.ca constitutes a series of successful transformation projects. These projects are a possible template for transforming government services to citizens. However, in the Buyandsell.gc.ca case, leading stakeholders never considered transformation their goal and at no time was their work managed as a transformation project.
Buyandsell.gc.ca is the result of an iterative process of discovery. The team asked open questions and was open to all possible answers. They eschewed traditional requirements definition and delivered incremental improvements guided by a strategic intent: to improve the user experience of tender management. By allowing tender creators and consumers to validate the improvements via real systems, and by accepting a long-term process of continued short-term iteration, a transformed system was made operational. That system is built upon loosely coupled foundation (platform) components that can be added to in order to deliver additional services without impacting Buyandsell.gc.ca itself.
While this approach remains unfamiliar to many in the federal government, it is based upon Agile methodologies widely used in the private sector. These techniques present a lower risk than the waterfall project management approach (the National Project Management System) traditionally use for federal government projects.
This presentation summarizes key Lessons Learned in the conception, design, implementation, and delivery of Buyandsell.gc.ca. It references best Agile practices in relation to its achievements.
The side effects of AgilityPierre LeBlanc
schedule 9 months agoSold Out!
Agility can provide great results or increase team performance. What about its side effects? My goal is to bring attention to all sorts of side effects, which are often underestimated during and after a transition towards Agility. From conflicts to good team spirit, from employee resignation to higher employee retention, you will definitely experience both negative and positive side effects.