Differences

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

--- what_are_the_changes_in_management_approach_that_need_to_happen_with_agile [2016/03/29 07:47] – hpsamios
+++ what_are_the_changes_in_management_approach_that_need_to_happen_with_agile [2020/06/10 12:47] (current) – ↷ Links adapted because of a move operation hans
@@ Line 15: / Line 15: @@
   - Independent of anything else going on, how will you increase collaboration?
-  - Accounting for everything else going on, how will you increase trial and actual deliveries to consumers?
+  - Accounting for everything else going on, how will you increase trial and actual deliveries to customers?
   - How will you get people to pause and reflect on what’s happening to and around them?
   - What experiments will your people do at different levels in the organization to make a small improvement?
-The role of management changes as well (for more see [[scrum_at_scale_-_jeff_sutherland|Jeff Sutherland's discussion on how management needs to change]]:
+The role of management changes as well (for more see [[scrum_at_scale_by_jeff_sutherland|Jeff Sutherland's discussion on how management needs to change]]):
-  * Provide challenging goals for the teams
+  * Provide challenging goals for the teams - something focussed, exciting, engaging.
-  * Create a business plan that works
+  * Create a business plan that works - based on reality of what you are seeing
-  * Eliminate organizational debt
+  * Eliminate organizational debt - such as structures that require working dependencies for every item of value we need to deliver to customers [[why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]]
-  * Orovide all resources a team needs
+  * Provide all resources a team needs - hardware, capability, training, tools.
-  * Identify and remove impediments for the teams
+  * Identify and remove impediments for the teams - and make sure you are seeing these impediments, that they are not being hidden.
-  * Know velocity of the teams
+  * Know velocity (capacity) of the teams - so you can understand the true capacity of your organization to deliver value and do not push too much work-in-progress (WIP)
   * Remove waste – eliminate technical debt
-  * Hold product owners accountable for value delivered per point
+  * Hold product owners accountable for value delivered (for example, per point) - which means they also need to be concerned about technical debt.
-  * Hold scrum master accountable for process improvement and team happiness
+  * Hold scrum master accountable for process improvement and team happiness - which means we have engaged teams.
 {{tag>Consultant Tools CultureChange Management Organization FAQ PresentationIdea}}
-~~LINKBACK~~
-~~DISCUSSION~~