Differences

This shows you the differences between two versions of the page.

--- johanna_rothman_-_scaling_agile_projects_to_programs [2015/08/20 07:22] – external edit 127.0.0.1
+++ johanna_rothman_-_scaling_agile_projects_to_programs [2015/08/20 09:13] – hpsamios
@@ Line 1: / Line 1: @@
-Title: JohannaRothman-ScalingAgileProjectsToPrograms Timestamp: 2015-08-03 15:55:29 +0000 Created: 2015-08-03 14:25:18 +0000 Last Accessed: 2015-08-03 14:25:18 +0000 Times Accessed: 0 Tags: Metadata: gpslongitude=-77.018415,gpslatitude=38.781039 # Premise
+====== Premise ======
 Are you trying to scale your agile project to a program, a collection of projects with one strategic objective? If you do what you’ve done with one small project, you’ll get bloat. Instead of bloat or large frameworks, you can use agile and lean approaches to manage your program with small-world networks. Small world networks help each team to remain autonomous, and still collaborate and explore across the program.
@@ Line 17: / Line 17: @@
   * Book - predicting unpredictable
-  * book - agile and lean program management
+  * Book - agile and lean program management
-  * how do encourage small world networks
+  * Understand how see, understand and encourage small world networks at work
-  * see epic progress chart (one chart with everything)
+  * Review epic progress chart (one chart with everything)
+{{:product_backlog_burnup_showing_progress_of_features_epics_as_well.png?200|}}
 ====== Presentation ======
+{{:agile_program_management.scalingcollaboration.key.pdf|}}
 Jr@jrothman.com @johannarothman Www.jrothman.com
@@ Line 150: / Line 154: @@
 Release often - see progress, invite collaboration Frequent releases encourage exploration It's agile / lean all the way across