Scrum of Scrums has a mixed record of effectiveness. The vast majority completly miss the point of stand-ups and Scrum of Scrums. The last few years have seen unscrupulous consultants sell all sorts of pills for the ills of scaling. If a project needs more than 15 people, it is crucial one understands the Central issue of scaling. 

In this talk I take the audience through the common pitfalls and explain the irrelavance of the question: "How can we scale agile?"

 

 

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Introduction (1 min)

Scrum of Scrum - Mike Cohn format (2 min)

The central Question (2 min)

unSAFe patterns and why we need LESS (2 min)

Why the SoS has such a poor record and the delusion supported by consultants (4 min)

Recommended Refinement based on experience (4 min)

The missing pieces of scaling (4 min)

Be safe and Godspeed (1 min)

Learning Outcome

Deep understanding of Scrum, what the use of this tool

 

Understanding the central issue of scaling and what scaling really means

Target Audience

Managers, consultants, coaches

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Howard Deiner
    keyboard_arrow_down

    Howard Deiner - Agility at Scale - Platform versus Product Concerns

    45 Mins
    Talk
    Intermediate

    A common failure mode for organizations attempting to adopt an Agile style of software development occurs when an attempt is made to “Scale Agile”. Suddenly, the organization finds that there are scheduling problems between teams. Delivery team members suddenly find that they are required to serve on several teams at once. Dependencies surface, and teams find it difficult to come together in a common cadence to produce working software in a continuously delivered fashion. Many times, these issues become so grave that the organization reverts back to the Waterfall model that they came to hate, but at least understood.

    This session explores Agile scaling concerns, and places particular emphasis on an architecturally significant distinction in the software to be created, and the components produced to allow the software to be created. That distinction revolves around cross cutting platform concerns versus product feature creation concerns. We will examine the distinctions and explore solutions that should help your organization get past these issues when it comes to portfolio management, by paying attention to extrinsic versus intrinsic value metrics.

  • Liked Prafulla Girgaonkar
    keyboard_arrow_down

    Prafulla Girgaonkar / Naresh Jain - eXtreme Programming for ETL and Data Analytics

    45 Mins
    Experience Report
    Intermediate

    Over the last decade, eXtreme Programming practices like User Stories, Evolutionary Design, Test-Driven Development (TDD), Behavior Driven Developer (BDD), Refactoring, Continuous Integration and Automation have fundamentally changed software development processes and inherently how engineers work.

    Having experienced various benefits from XP practices on our J2EE stack, our team started to apply these practices to extract, transform, and load (ETL) and Data Analytics side of our product. Unfortunately, there is very little guidance available in this context, esp. for the SAS Platform. Right from finding the unit testing framework to structuring the code to designing our modules and setting up a Continuous Integration builds, our team had to figure out everything, the hard way.

    Join us to understand the challenges we faced during this process and how we resolved these challenges.

  • Liked Howard Deiner
    keyboard_arrow_down

    Howard Deiner - Lean Thinking and What It Mean to the Agile Mindset

    45 Mins
    Talk
    Intermediate

    Long before the Agile revolution for software development began, industry had learned that efficient production of goods required intense attention to quality, teamwork, and continuous improvement. These themes of Lean Manufacturing (which was further refined into the Toyota Production System) were never part of the original formulation of the Agile Manifesto, and are rarely mentioned as part of the traditional Agile/Scrum recipe for teams transforming to the new “Agile” mindset.

    The reality is that the traditional Agile/Scrum recipe is actually a “dumbed down” version of the Toyota Production System, and makes it easier for organisations to grasp and start from. However, if organisations really want to achieve the goal of producing the software they need in a fashion that leads to High Performance Teams and Sustainable Engineering, they will need to understand the principles of Lean so they can incorporate them into their unique process. This session teaches the basics of Lean, and demonstrates how they apply to Agile development.

  • Liked Nilotpal Das
    keyboard_arrow_down

    Nilotpal Das - Head First Agile and Organizational Transformation

    45 Mins
    Experience Report
    Intermediate

    This is a collection of real time case studies of failed projects. It is an autopsy of these failed projects studying why these projects failed and how application of agie principles could have saved them.

    It is also a study into the organizational culture, behavioral attributes and the people issues and how agile addresses them.

    And finally it is a study of why doing a few projects with agile is not sufficient. How complete organizational transformation into agile practices is necessary for long term success for projects, processes and people.