Agile and Lean Program Management chapters
About this audiobook · Recording details
Recording zoe-walrond-2016 · Narrated by Zoe Walrond
Showing 63 of 163 chapters
| Chapter | Title | Start | Duration |
|---|---|---|---|
| 101 | 10.8. Measure Build Time | 3:30:49.789 | 0:00:56.960 |
| 102 | 10.9. Other Potential Measurements | 3:31:46.749 | 0:04:08.010 |
| 103 | 10.10. Measure Performance or Reliability Release Criteria | 3:35:54.759 | 0:01:32.010 |
| 104 | 10.11. How to Answer the “When Will You Be Done/How Much Will Your Program Cost” Question | 3:37:26.769 | 0:02:42.980 |
| 105 | 10.12. Principles | 3:40:09.749 | 0:01:12.082 |
| 106 | 11. Develop Your Servant Leadership | 3:41:21.831 | 0:00:59.800 |
| 107 | 11.1. Program Managers No Longer “Drive” the Program | 3:42:21.631 | 0:00:58.223 |
| 108 | 11.2. Consider Your Servant Leadership | 3:43:19.854 | 0:01:40.730 |
| 109 | 11.3. How Servant Leaders Work | 3:45:00.584 | 0:02:30.980 |
| 110 | 11.4. Some People Don’t Want Servant Leadership | 3:47:31.564 | 0:02:41.380 |
| 111 | 11.5. Welcome Bad News | 3:50:12.944 | 0:03:52.910 |
| 112 | 11.6. Use the Growth Mindset | 3:54:05.854 | 0:00:45.360 |
| 113 | 11.7. Ask For the Results You Want | 3:54:51.214 | 0:02:28.770 |
| 114 | 11.8. Principles of Develop Your Servant Leadership: | 3:57:19.984 | 0:00:39.979 |
| 115 | 12. Shepherd the Agile Architecture | 3:57:59.963 | 0:02:05 |
| 116 | 12.1. Architects Write Code | 4:00:04.963 | 0:04:03.812 |
| 117 | 12.2. Many Developers Become Architects | 4:04:08.775 | 0:01:16.520 |
| 118 | 12.3. Encourage Iterative and Incremental Architecture | 4:05:25.295 | 0:02:49.390 |
| 119 | 12.4. Architects Can Help Expose Risks | 4:08:14.685 | 0:02:34.350 |
| 120 | 12.5. What the Program Architect Accomplishes Daily | 4:10:49.035 | 0:02:41.210 |
| 121 | 12.6. Architecture Is a Social Activity | 4:13:30.245 | 0:01:42.140 |
| 122 | 12.7. Problems You May Encounter with Architecture | 4:15:12.385 | 0:03:51.860 |
| 123 | 12.8. Break the Architecture with Purpose | 4:19:04.245 | 0:01:50.990 |
| 124 | 12.9. Principles of Shepherd the Agile Architecture | 4:20:55.235 | 0:00:52.105 |
| 125 | 13. Solve Program Problems | 4:21:47.340 | 0:00:31.400 |
| 126 | 13.1. Ask For the Problems or Impediments First | 4:22:18.740 | 0:03:04.971 |
| 127 | 13.2. People on the Core Team Don’t Deliver What They Promise | 4:25:23.711 | 0:00:58.120 |
| 128 | 13.3. Your Product Owners Have Feature-itis | 4:26:21.831 | 0:02:01.610 |
| 129 | 13.4. People on Teams Are Multitasking | 4:28:23.441 | 0:01:54.220 |
| 130 | 13.5. How to Start a Program with More People Than You Need | 4:30:17.661 | 0:04:33.650 |
| 131 | 13.6. Principles of Solve Program Problems | 4:34:51.311 | 0:00:48.975 |
| 132 | 14. Integrating Hardware Into Your Program | 4:35:40.286 | 0:01:11 |
| 133 | 14.1. Hardware Risks Are Different than Software Risks | 4:36:51.286 | 0:01:06.471 |
| 134 | 14.2. Understand Cost and Value for Hardware | 4:37:57.757 | 0:03:20.690 |
| 135 | 14.3. Understand Each Part’s Value | 4:41:18.447 | 0:02:32.620 |
| 136 | 14.4. See the Work | 4:43:51.067 | 0:01:02.360 |
| 137 | 14.5. Design Incrementally and Iteratively | 4:44:53.427 | 0:00:38.360 |
| 138 | 14.6. Use Continuous Design Review | 4:45:31.787 | 0:01:16.530 |
| 139 | 14.7. Integrate Hardware Often | 4:46:48.317 | 0:01:54.040 |
| 140 | 14.8. Manage Hardware Risks | 4:48:42.357 | 0:02:15.650 |
| 141 | 14.9. Develop the Software Before the Hardware Is Available | 4:50:58.007 | 0:03:28.360 |
| 142 | 14.10. Principles of Integrating Hardware Into Your Program | 4:54:26.367 | 0:00:37.912 |
| 143 | 15. Troubleshooting Agile Team Issues | 4:55:04.279 | 0:00:40.600 |
| 144 | 15.1. The Teams Are Not Feature Teams | 4:55:44.879 | 0:07:23.080 |
| 145 | 15.2. Teams Think They Are Agile, But They Are Not | 5:03:07.959 | 0:10:12.030 |
| 146 | 15.3. The Teams Have Dependencies on Other Teams | 5:13:19.989 | 0:01:54.230 |
| 147 | 15.4. Your Features Span Several Iterations | 5:15:14.219 | 0:01:17.770 |
| 148 | 15.5. You Don’t Have Frequent-Enough Deliverables | 5:16:31.989 | 0:01:14.880 |
| 149 | 15.6. Teams Don’t Finish When They Say They Are Done | 5:17:46.869 | 0:04:02.370 |
| 150 | 15.7. Principles of Troubleshooting Agile Team Issues | 5:21:49.239 | 0:00:45.444 |
| 151 | 16. Integrating Agile and Not-Agile Teams in Your Program | 5:22:34.683 | 0:01:27.300 |
| 152 | 16.1. Waterfall Teams Are Part of Your Program | 5:24:01.983 | 0:03:57.141 |
| 153 | 16.2. You Have Teams that Produce Incrementally, But Not in an Agile Way | 5:27:59.124 | 0:00:58.440 |
| 154 | 16.3. You Have Teams that Prototype and Don’t Complete Features | 5:28:57.564 | 0:01:17.850 |
| 155 | 16.4. Principles of Integrating Agile and Not-Agile Teams in Your Program | 5:30:15.414 | 0:01:10.030 |
| 156 | 17. What to Do if Agile and Lean Are Not Right for You | 5:31:25.444 | 0:02:21.500 |
| 157 | 17.1. Try an Incremental Life Cycle | 5:33:46.944 | 0:03:31.010 |
| 158 | 17.2. Organize by Feature Team | 5:37:17.954 | 0:01:37.150 |
| 159 | 17.3. Learn to Release Interim Deliverables | 5:38:55.104 | 0:01:12.050 |
| 160 | 17.4. Learn How to Reduce Batch Size with a Large Program | 5:40:07.154 | 0:01:18.670 |
| 161 | 17.5. Try Release Trains | 5:41:25.824 | 0:05:02.170 |
| 162 | 17.6. Principles for What to Do if Agile and Lean Are Not Right for You | 5:46:27.994 | 0:02:57.641 |
| 163 | End Credits | 5:49:25.635 | 0:00:38.172 |