Al Shalloway alshall-F2W/AIYyHykAxtNtZnumnAC/G2K4zDHf@public.gmane.org [seajug]
2014-06-20 11:56:10 UTC
Sorry for the last minute email but I realized I had forgotten to announce this latest webinar in our What is Required at Scale<http://www.netobjectives.com/events/effective-agile-at-scale-webinars-what-is-required-at-scale-2014-06> which discusses those actions that must be undertaken to be successful at scale. This talk is not about a particular approach, but what needs to be accomplished. Our next webinar (to be scheduled soon, will be on the value of teams, register at www.netobjectives.com/register<http://www.netobjectives.com/register> to be personally notified).
While these may not have been well-known 10 years ago, they are fairly well known now and include:
Business Level
* Focus on building and deploying minimal business increments
* Drive from business value, organize around what is being built and build incrementally
* Have architectural epics be a peer to business epics
* Limit the number of things being worked on
Management
* Make all work visible
* Have teams work in a consistent cadence to be able to synchronize on a frequent basis
* Value code quality, program execution, alignment and transparency
* Provide a structure for teams to work together
* Create teams to the greatest extent possible
Teams
* Manage work in process to eliminate waste caused by delays and overworked people
* Have an owner for the development value stream
* Use test-first methods
* Automate testing
* Achieve continuous integration
Intended audience: Directors, Executives, Project Managers, ScrumMasters, Team Leads, Architects
Click here<http://www.netobjectives.com/events/effective-agile-at-scale-webinars-what-is-required-at-scale-2014-06> to register.
Al Shalloway
CEO, Net Objectives
While these may not have been well-known 10 years ago, they are fairly well known now and include:
Business Level
* Focus on building and deploying minimal business increments
* Drive from business value, organize around what is being built and build incrementally
* Have architectural epics be a peer to business epics
* Limit the number of things being worked on
Management
* Make all work visible
* Have teams work in a consistent cadence to be able to synchronize on a frequent basis
* Value code quality, program execution, alignment and transparency
* Provide a structure for teams to work together
* Create teams to the greatest extent possible
Teams
* Manage work in process to eliminate waste caused by delays and overworked people
* Have an owner for the development value stream
* Use test-first methods
* Automate testing
* Achieve continuous integration
Intended audience: Directors, Executives, Project Managers, ScrumMasters, Team Leads, Architects
Click here<http://www.netobjectives.com/events/effective-agile-at-scale-webinars-what-is-required-at-scale-2014-06> to register.
Al Shalloway
CEO, Net Objectives