Join the thousands of people defining the future of software development by taking part in Atlassian’s global agile retrospective. #RetroOnAgile
Follow, research and publish the best content
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
Devops for Growth
112.9K views |
+9 today
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by
Mickael Ruau
 Your new post is loading...
Your new post is loading...
Scoop.it!
Once all your teams use Agile and are busy implementing local improvements, what happens to the larger organization formerly called "IT" or "Systems Development"? A coach with a large Agile program shared the strategy they designed to let the larger community spot trends and benefit from all this learning. Paulo Caroli calls it "Retrospective of Retrospectives".
Mickael Ruau's insight:
Caroli's solution draws on the wisdom of Scrum of Scrums: Retrospective of Retrospectives, which they shortened to RoR. Similarly to how the daily scrum is extended to the Scrum of Scrums ... I came up with the idea of having a Retrospective of Retrospectives for large Agile teams. ...the RoR context is: "What can we do as one team (the whole program team) to improve the overall output for the program?" 
|
Scoop.it!
Retrospectives are one of the many powerful tools to review and improve your team’s approach to solving problems. For many project teams, they do a retrospective at the end of every 1–2 weeks. If…
|
Reflect on your software development experience and follow the following links to twitter:
Check out the thousands of responses we’ve gotten so far.