Scaling Scrum to the Enterprise Webinar Series

Error message

Strict warning: Declaration of role_expire_handler_field_rid::pre_render() should be compatible with views_handler_field::pre_render(&$values) in require_once() (line 83 of /home2/netobje2/public_html/sites/all/modules/role_expire-7.x-1.0-beta2/role_expire/role_expire.views.inc).

Scaling Scrum to the Enterprise
Free 3-Part Webinar Series

This series is over. The recorded webinars are available to Registered users.


Part I - Monday, July 21st
Management Track: Process - 11 am PDT
Scaling Scrum to the Enterprise with Lean Software DevelopmentClick here to see it if you missed it
(note: you must have registered to gain access to it).
This webinar introduces how to scale Scrum to the Enterprise with Lean Software Development. Lean Software Development extends Scrum with Lean Principles and the best practices of Emergent Design. This webinar presents a broad stroke of Lean Software Development. The following webinars dive down deeper. Here we'll give a high view of the process and analysis extensions of Lean Software Development. These include:
  • Shifting the focus from team and project to enterprise and product
  • Managing your product portfolio across the enterprise
  • Using the entire development organization as the context for your agile process
  • The importance of Minimum Marketable Features
  • Managing the need to look ahead in time and across teams in Scrum
  • The need for an organization wide team to manage dependencies between teams

Technical Track: Design & Programming - 1 pm PDT
Design Patterns in an Agile EnvironmentClick here to see it if you missed it
(note: you must have registered to gain access to it).
This webinar breaks the myth that every iteration must be focused on customer value. No customer value is delivered until the release. While releases should be based on customer value, individual stories should be based on a combination of customer value, risk mitigation and business value. This webinar relates an actual project where quality coding techniques were used to manifest the Lean principles of optimize the whole, deliver fast, defer commitment, build quality in and create knowledge. This session covers:
  • Using encapsulation to defer commitment
  • The need for risk mitigation in picking stories
  • How to decide what stories to work on when customer value can't do it

Part II - Monday, August 18th
Management Track: Process - 11 am PDT
Managing Requirements in Lean Software DevelopmentClick here to see it if you missed it
(note: you must have registered to gain access to it).
This webinar discusses how Lean Software Development's enterprise and product focus improves on the standard method of managing with Epics and User Stories. By stepping back to include product portfolio management, Lean Software Development facilitates working on the right product features across the enterprise, not just working on the right stories in a project. Topics discussed include:
  • Product Portfolio Management with Minimum Marketable Features (MMF)
  • How MMFs are more useful than Epics
  • Going beyond user stories
  • Managing stories from business value
  • Handling time and team dependencies in your Sprint backlog

Technical Track: Design & Programming - 1 pm PDT
Avoiding Over and Under Design in Agile ProjectsClick here to see it if you missed it
(note: you must have registered to gain access to it).
This webinar focuses on what developers must attend to when building systems with Agile methods. It discusses an alternative to the choices of:
  • Design for the future which often results in overdesign
  • Not designing at all which often makes code difficult to change
The mantra of the talk is “minimizing complexity and rework” and shows how to use the advice from Design Patterns, coupled with the attitude of not building what you don’t need from Agile. The talk is basically a compendium of the essential ideas Net Objectives believes that developers need to understand after learning the basics of Scrum or Agile process. At the end of the day, you are still writing code. This webinar is a first start in what you need to know in writing code in an Agile environment.
Attendees will learn:
  • How Design Patterns give an alternative design approach to the common approaches of over and under design
  • How decoupling modules from the start can often be done in a simple manner without requiring pre-cognitive abilities
  • How the understanding of components written by one group and used by another can be defined better

Part III - Tuesday, September 2nd
Management Track: Process - 11 am PDT
Understanding Why Scrum WorksClick here to see it if you missed it
(note: you must have registered to gain access to it).
This webinar discusses why Scrum works and how Lean's metaphor of Fast-Flexible-Flow can be used to modify standard Scrum practices as needed. Additionally, the enterprise view and Lean Management philosophy will be the basis for creating an Enterprise/Organization wide team to manage dependencies across teams without command and control. This webinar covers:
  • Why Scrum works
  • How Lean-Thinking can identify root cause of problems
  • How to use Lean-Thinking to eliminate delays
  • Breaking down the silos between development and Quality Assurance
  • How to coordinate multiple development teams so that they work together - going beyond Scrum-of-Scrums

Technical Track: Design & Programming - 1 pm PDT
Avoiding Coupling and Using Mocks in Agile EnvironmentsClick here to see it if you missed it
(note: you must have registered to gain access to it).
While full up-front designs are not the proper approach in virtually all agile projects, no design up front can also be a problem. This webinar discusses some techniques for decoupling modules early on. In other words, although we may not know how things will change, we often know of dependencies between modules that will morph over time. This webinar presents three case studies:
  • Decoupling informational dependencies between components
  • How to define the API for a component being built by one group and used by another
  • Using mocks to never be blocked - avoiding delays caused by dependencies of different tiers