Scale, the most hyped term today, but really, how do you scale successfully?
Scrum is everywhere, with over 90% of agile teams using it. But for many organizations wanting to scale agile, one team using Scrum is not enough. Scrum is not enough. The Nexus Framework, created by Ken Schwaber the co-creator of Scrum, provides an exoskeleton to Scrum, allowing multiple teams to work together to produce an integrated increment regularly. It addresses the key challenges of scaling agile development by adding new yet minimal events, artifacts and roles to the Scrum framework.
In this talk, we introduce the Nexus Framework and how it, like Scrum, promotes bottom-up thinking with top down support in order to discover and emerge what works best for your organization. We will use case studies as examples to describe Nexus in detail showing how it works, how it is working, and what its strengths and weaknesses are. The audience will be taken through Nexus, its new events and the key role of the Nexus Integration Team.
Outline/structure of the Session
Why we created the Nexus Framework and Scaled Professional Scrum at Scrum.org
Walk through of Nexus Framework / examples of Nexus in action / practices to consider
When scaling, start with Professional Scrum (understand Scrum Mechanics + technical excellence + Scrum Values)
Techniques to remove and minimize dependencies when scaling Scrum between multiple Scrum Teams.
Understanding of the Nexus Framework - rules, roles, events, artifacts.
Anyone involved in formulating, participating or managing scaled Scrum product development
schedule Submitted 11 months ago
People who liked this proposal, also liked:
The Geek's Guide to People - Shifting from Output to ImpactSue Johnston
schedule 10 months agoSold Out!
The stereotype of technical professionals as inarticulate, socially inept geniuses inventing problems to solve is unkind and inaccurate. Yet the Dilbert image persists. So do jokes like the one about the engineer sentenced to death on the guillotine, who watches the instrument of death malfunction, then tells the operators how to fix it.
Why do people make fun of engineers and those with their mindset? Do people wired and trained to analyze and solve problems and focus on the mechanics of a situation frustrate those whose brains are wired differently? And how does the engineer’s way of dealing with individuals and interactions - that first value of the Agile Manifesto - sometimes get in the way of team collaboration and productivity?
In this interactive session, we'll show a little empathy for engineers and other analytical folk whose neurological wiring makes them seem different from the rest of humanity. We'll also explore how those with the engineering mindset can develop their own empathy and consciously adopt behaviours that amplify their value to their teams and organizations, make them more effective leaders - and make their own lives easier by positioning themselves for understanding.
Join Sue in a lively exploration of what can happen when engineers and technical professionals shift their mindset from solving problems to creating impact.
You will leave this session with an appreciation of:
- How to make your ideas meaningful to others by taking their perspective
- How shifting your language from "What?" to "So What?" helps people connect the dots
- Why giving up the need to be smart may be the smartest thing you ever do
- Techniques you can use to take someone else's perspective.
From dysfunction to cross-function in 8,593 easy steps: Team building at the CBC
When it comes to scaling Agile, there is no one size fits all solution. Frameworks like Scrum and XP prescribe roles, events, artifacts, and rules that make it very clear how interaction should take place within a team. When we begin to add more teams to the mix, communication between teams becomes more complex. This complexity threatens to reduce our transparency and damage our culture. How can we share information, build our culture and work together, all while keeping with Agile values?
During this session Sam Lightowler and Jade Stephen will take an in depth look at the successes and failures of CBC Digital Operations when it comes to cross-team collaboration and information sharing. We will discuss what meetings and techniques have helped us build a one-team-one-product mindset, a sense of community, and a culture of Collaboration, Learning and Improvement. We will also discuss what we have tried in the past and how learning from those experiments helped us evolve into the agile-friendly and unified team that we are today.
A Federal Government Shared Service Success Story: Buyandsell.gc.caKen McMillan, PMP, CISSP, ITIL, MIPIS, PCIP
schedule 9 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.
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
Agile for Normal People - non-technical teams need agile too!Rob Villeneuve
schedule 10 months agoSold Out!
Agile is alive and well in the technical sphere, but why should we stop there? At the root of it teams from every discipline are simply a group of people working together to reach their goals. Their subject matter is unique but the challenges are not. We are all normal.
Rob Villeneuve is a software developer turned CEO, and who used Agile to empower a team of 50+ at rebel.com. This first hand account will share the transition story of rebel.com from a few agile teams into an Agile Organization. We will explore the rewards of thinking agile at every level, from leadership to the front line, and Rob will share experiences from each department at Rebel embarking on their own Agile journey. If you wish others in your organization would simply try agile, or would improve their understanding of why you agile, then you may have something to learn from the cross-training experiences of introducing agile to non-technical teams.
Rob has introduced agile to teams of many sizes, disciplines, and experience levels including: Board of Directors, Leadership Teams, Sales, Marketing, Finance & Accounting, Customer Service/Call Centre, Software Development, Network Operations, and Architects (Building Architects).
My Agility is bigger than yoursJean-René Rousseau
schedule 10 months agoSold Out!
The word "Agile" is all over the place now. Discussions are not only about if you are doing it, but mostly about how you are doing it. And in those conversations I often feel people are trying to prove hey are doing better than others. But when we compare our agility, what do we really whant to know? How can I say that my agility is bigger than yours?
Over the last 13 years doing agile software development and specially during the last 8 years as an agile coach I had the chance to explore this question on how to measure the teams and organisational agility through diverse tools and techniques with multiple customers and teammates. During this conference I would like to share with you those experiences and reflect on how to measure your agility. Maybe you should not only look on how you are doing agile development, but more on what is the impact of it!
The Agility Series: Organizational Agility + Leadership Agilitylawrence cooper
schedule 9 months agoSold Out!
Larry Cooper recently launched The Agility Series which covers nine areas of agility:
- Organizational Agility
- Leadership Agility
- Cultural Agility
- Strategic Agility
- Value Agility
- Delivery Agility
- Business Agility
- Client/Customer Agility
- Learning Agility
Each area of agility is being tackled in separate books whose ideas and contents are being crowd sourced. Larry worked with the dynamic team at www.GreatWork.io (a local Ottawa company) using their on-line tool to ask powerful questions, gather ideas and then to converge the ideas into 4-5 phrases for each question which the contributors then prioritized. The books provide insights into the ideas offered and the prioritizations of the group.
For the first book on Organizational Agility Larry approached a group of senior leaders he knew from a broad spectrum of industries, sectors and countries to participate in a Wisdom Council to answer a series of questions. He then created a LinkedIn group for the Series and expanded the scope of contributors for the next book on Leadership Agility (over 70 contributors) and hopes to keep expanding the number of contributors for each subsequent book.
In the session Larry and Jen Hunter from GreatWork will share the insights they gathered on Organizational Agility and Leadership Agility. Organizational Agility focused on six topic areas:
- The primary waste in traditionally run organizations
- The greatest challenge facing organizations that want to become more agile
- The values that all agile organizations would exhibit
- The principles that are the most important for an agile organization to focus on
- The primary trait or characteristic of an agile organization
- How they would describe organizational agility to a colleague
Leadership Agility focused on five main topic areas:
- The key obstacles traditional leaders will need to overcome in the 21st century
- The key differences between leadership and management
- The key behaviors that are exhibited by agile leaders
- The core values that an agile leader demonstrates
- The phrases that would that best describe an agile leader
The contributors to Leadership Agility were also asked to offer their own powerful questions that we could ask of them. We chose 4 additional questions to ask of the group and Larrywill share the those results as well.
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.
Scaling Agile - Adventures with SAFeAnnette Lee
schedule 10 months agoSold Out!
If you have multiple scrum teams working together to deliver business value, you'll be thinking of moving to Scaled Agile. In our company we have a number of different product lines all running with multiple scrum teams. We needed a way to roll up all of that information and track the progress of our releases. We also needed to do roadmap planning. In this presentation, I'll go over our learning curve in Scaled Agile and our experience with SAFe (Scaled Agile Framework).
A case study in scaled and self-organized ScrumSean McFee
schedule 10 months agoSold Out!
A green fields development project presented a good opportunity to experiment with an agile way of work involving increased team self-organization. Initially this involved confronting a traditional command-and-control approach with something based more closely on the Scrum Guide, while surmounting a number of impediments that are common to many organizations. Over time, as the project grew, scaling problems were discovered and had to be dealt with, ranging from simple things like meetings to more complex issues like team composition.
Servant Leadership, are women the better fit?Patricia Kong
schedule 11 months agoSold Out!
Do women make better Scrum Masters, because they’re more nurturing? Do women have to be aggressive in order to be effective leaders? Why aren’t women good risk takers? Let’s explore these topics, other stereotypes, and different myths and facts that surround the female role in agile and technology. Patricia Kong from Scrum.org and Jill Graves from the Canadian Revenue Agency will share their experiences and facilitate this discussion to explore why women are stalled in leadership roles and in the technology industry, and if Agile can help.