Open Space gatherings arranged inside organizations are totally unlike the Open Space events you may be familiar with during public conferences. As described in the book SPIRIT from Harrison Owen, Open Space is actually designed to enable development and transformations in organizations. This session is about how to leverage Open Space to scale Agile across the enterprise.

At the root of effective Agile is the self-managed team...a self-organizing system. At the core of Open Space is the power of self-organization. In this sense, effective Agile adoptions and Open Space are very, very similar.

During this session I will present narratives, pictures, videos and testimony from C-level people as well as team members. Each will describe how Open Space inside their Agile adoption literally changed their lives. Of particular interest are the stories executives tell about how they learned to let go and trust their people to provide everything the Agile adoption needed to succeed at scale.

User story mapping is a useful technique which helps the teams with a product backlog visualization.             

It enables a Product Owner to carry on discussions with business stakeholders and development teams at the appropriate levels of granularity.

It helps the team to identify and build “vertical slices” of the system every Sprint, simplifies MVP and a release planning.

In this session, we will give a short user story mapping primer and highlight the advantages of using this approach over the traditional flat backlog.

Using FeatureMap tool as an example, we will demonstrate how user story mapping can be successfully applied in a distributed team environment.

In this experience report we will demonstrate story maps created for software products as well as the story map we built for Big Apple Scrum Day.

There was a time when scaling Scrum was daunting to organizations.  Not anymore.  Organizations are going all in on the scaled agile approach; whether it be SAFe, LeSS, or DAD.  There are some pitfalls but none that outweigh the benefits when scaling is appropriate.

In this talk, we will discuss the different approaches to scaling Scrum and what can be borrowed from each.  In addition, we will discuss the business case for scaling.  Finally, Jim will present some of the approaches that Rally's coaches and transformation consultants have employed to successfully launch organizations on their scaled Scrum adoption.

Is scaling Scrum inevitable?  No, you still need to match your capacity to the demand.  But, when the demand is there, the approaches are there to meet the demand.

All too often, companies set out with the mission to “go agile” before truly understanding what that means. Business managers are quick to jump on the agile bandwagon, believing that “going agile” will magically make projects happen faster. Teams are getting certified in Scrum as if it’s a silver bullet that will suddenly make everyone more productive. Inevitably, cracks begin to show, and expectations are missed--leaving everyone involved questioning the value of “going agile” altogether.

There is a better way! The truth is that going agile will result in more productive teams and faster delivery of projects--but only if everyone can agree on the rules of the game.

Come hear Heather Fleming and Justin Riservato from Gilt discuss why gaining consensus on the principles of Agile is more important than implementing a process, and learn how having these three conversations can save you from an agile disaster:

• “But when will you be done?”  Why getting rid of the concept of deadlines is the most important (and most difficult) conversation when going agile.
• “This is my top priority, but I can’t meet with you until next week.”  What to do when your business partner can’t (or won’t) be a full member of the team.
• “I just want to code. Why do I have to be in all these meetings?”  Why implementing Scrum is not the first step to going agile.

"As a user of your system, I want functionality so that I can achieve my goals. Unfortunately, your team's users stories are getting in the way."

Users Stories, the tool teams use to break ideas into small chunks of deliverable work, are easy to describe and challenging to write. This session is about writing great user stories and acceptance criteria by ensuring everyone on the team knows what needs to be done. We will discuss what elements should be included and which ones are optional; why the size of your user story is important and how to make them smaller; and the structure for better acceptance criteria.

Executives believe starting their project NOW means it will end sooner. Unfortunately, starting one more project costs dramatically more than waiting. Sharing limited resources causes all the projects to sub-optimize. Multitasking is costing your organization a fortune!

Are you tired of being time-sliced across too many projects? Learn how value decreases when you work on many projects at the same time and increases (!) when you focus and deliver on a single project.

Come, play a game based upon ideas from Critical Chain Project Management, Lean, and Agile. Take part and help us illustrate the power of focus on your project portfolio management.

Do you remember the frustration that comes from trying to make traditional HR instruments like performance reviews work for your Agile teams? Do you feel HR is undermining your best efforts at collaborative leadership and is holding you back? Do you find yourself in a constant dispute with HR over people processes?

It is inevitable: HR must embrace Lean | Agile values and principles in order to engage and energize Agile talents. It’s time to show HR how key people challenges like retention, talent development, and performance management can be addressed successfully with Lean | Agile.

Join this session to

– gain valuable insights into the world of Human Resource Management

– recognize the impact of Agile HR practices through stories and examples

– discover why Agile needs HR and vice versa

– identify compelling arguments and tactics to convince HR to go Agile.    

For years, Scrum/Agile coaching has been an attractive career for many. It is frequently viewed as a continuation of a career for an experienced Scrum Master who understands the intricacies of the cultural change that makes Scrum teams successful, knows nuts and bolts of a Scrum engine, and has natural aptitude for knowledge sharing and growing others. A leader who is unselfish and acutely self-aware, who has experience, and ability to influence others.  Many Scrum practitioners saw this role as their next step in professional development. The 2010 book, Coaching Agile Teams by Lyssa Adkins’ and her Agile Coaching Institute made Agile Coaching a discipline rather than a buzzword. Now, five years later, Agile Coaching is rapidly losing its attractiveness as a professional career. In her open-space style talk based on a retrospective with the session participants, Mariya Breyter will explore why this is happening and what a natural career progression for an Agile coach is. Agile Coaches and Scrum practitioners will exchange their experience and discuss their paths for professional development.

Scrum is by far the dominant Agile methodology and has been put to good use to positively change many software development groups. Some have found that even when they follow all the Scrum practices, they are still having some challenges, and they have turned to Kanban for help. Kanban is often framed as an alternative to Scrum, but it need not be so. Organizations using Scrum can augment their process with the Kanban Method to become more agile and delivery-oriented.

Jonathan Hansen will use real-world examples, both from product and consulting companies, to show you some of the ways Kanban can work together with Scrum to help you manage the work inside Sprints, manage work that doesn’t fit in Sprints well, and provide a means to continuously improve your work.

Parlez-vous Agile?

Sprechen sie Scrum?

Agile methods originated in technical practice, and its roots are solidly planted in the fertile ground of software engineering. Certifications in Scrum all require understanding of engineering practices, and the more senior level certifications require both in-depth understanding and practical application.  The message would seem to be that Agile practitioners must be Software Engineering practitioners. However, non-technical teams are adopting agile methods as ways to better organize – or, more accurately, self-organize – in increasing numbers.

As the language and history of agile is so strongly steeped in software engineering, applying agile methods in a non-technical setting requires some translation to be applied in a non-technical team.  I'm not just talking about jargon translation here; the methods and practices themselves sometimes need a tweak to work outside software engineering. The use of agile and scrum is not a slam-dunk success in every setting - be it technical or non-technical - but in this talk, I will separate myth from reality and give some practical examples from my own experience.  I invite you to join to learn, to contribute, and to discuss the opportunities as well as the effort required to leverage Agile/Scrum for a non-technical team.  

You often hear people ask, "Does the ScrumMaster role need to be a full-time role?". Obviously, the answer is yes. And you can point to results that you should expect to see from teams served by full-time, dedicated ScrumMasters. And you can detail the different aspects of the role that require such dedication. But the root of the issue is a misunderstanding of the ScrumMaster role.

One the surface, the ScrumMaster role is relatively simple; to serve the team by removing obstacles, facilitating meetings and coaching. Dig deeper, and the role becomes far more nuanced. The ScrumMaster role is one of nurture and change.

This session analyzes the ScrumMaster role through the lens of choice as an outcome. That is, that the role of the ScrumMaster is to facilitate the choice of an individual to be agile. The role of the ScrumMaster is to enable the behaviors that lead to agility, within the team and the organization.

You’ve read all the industry books, you’ve gotten your certifications and now you have a team staring at you waiting for you to take the lead. There is no hesitation about how to perform the basics -- determining roles and scheduling meetings -- but how do you take an ordinary team and kick start an effective, high performing team?

Whether you have a brand new team or you’re the new guy on an existing team, the tools and techniques you will learn in this session have proven to be effective from not-for-profits and state government to private sector insurance.

As an accredited Leadership Gift Coach Jessica focuses on vocabulary, shared responsibility, team agreements, and utilizing gamification to set the stage for a powerful and effective team no matter what methodology they use. 

If you’re practicing scrum, you’re probably well versed in velocity, escaped defects and other common scrum metrics.  This presentation starts with a review of essential scrum metrics, how to properly use them, and how to interpret their trends.  We’ll then quickly pivot into advanced and emerging metrics that many scrum teams (and programs) have found beneficial - examples include: how to measure and quantify the cost of delay when your team is blocked, how to ensure your team is investing the right amount of time to maintain clean code and create automated test scripts, and how to assess that your team is sharing work to support the whole-team approach.  We’ll review a comprehensive taxonomy of scrum metrics and show examples of presented metrics in use.  We’ll conclude talking about opportunities to better empower scrum teams to self manage by integrating economic and budgetary data with scrum metrics - consider this example: rather than reviewing estimates & actuals for all the stories completed in a sprint, determine your team run rate and track the cycle time for each story completed, then use these two data points to compute the cost for each story completed during a sprint, finally ask yourself if your customer or sponsor would be happy with the amount they invested to complete each story - if you’ve never tried this type of economic analysis with your team, trust me, you’ll have a much different (and probably more effective) discussion.  By attending this session, participants will learn a comprehensive list of metrics and practices to gain greater insights to team / project health and reduce delivery risk - participants attending will receive a metrics worksheet that will list all metrics presented and include why and how to track each of them.

Everyone knows that scrum works best when the entire team is sitting together in the same office. But the reality of today's working world is that more and more teams are geographically distributed. In many cases, this is the result of "strategic priorities" from senior management and is entirely inflexible. As scrum practioners, we must come up with strategies for adapting scrum to a distributed world. This talk will take a hypothetical distributed scrum team from release planning all the way through to launch day. What are some of the problems that will come up? What are the best ways of overcoming these issues? How should Scrum Masters facilitate sprint planning, sprint reviews, and sprint retrospectives? 

After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

Lego Scrum will provide an interactive learning experience enabling participants to learn about Scrum by seeing it in action.

Who should attend? Anybody wanting to increase their knowledge of Agile and Scrum, it’s non-technical  and is designed to be understood by everyone. 

These sessions represent what Macmillan Science and Education conduct regularly throughout their business to help build a wider understanding and awareness of Agile and Scrum.

Young, overly-confident and tech-savvy Millennials are challenging their colleagues and managers – just like the generation before them and they before them. But for the first time we are dealing with up to four different generations within one team.

That makes generational differences very real; causing misunderstandings and tension. And the hard realities of the «Unique Snowflake Syndrome» make it even more challenging for young professionals to find their place in the workforce.

Join this session to gain a better understanding of the «Snowflake Generation» and how Agile is the perfect blueprint to embrace diversity of thought and bridge the generation gap to shape unbeatable teams.    

The transition of Waterfall to Agile methodologies is never easy. The Waterfall approach consisted of these documents as a way to analyze the User needs: BRD (Business Requirement Documents), FRSs (Functional Requirement Specifications), SRS (Software Requirement Specifications), PRDs (Product Requirement Documents), etc. After the initial agreements, the development starts. In Scrum, the most important artifact to map User needs is the User Story. However, sometimes, the User Story is too big or too small or too abstract or never ending. This often lands the teams in difficult situations. So, it is vey crucial to Identify the Ideal Bite Size -- to identify the ideal size of our User Stories, yet keeping these Effective!