Agile Retrospectives based on Continuous Process Improvement
Agile Retrospectives are talked about and practiced my many teams, at varying levels across the globe. But more often than not, while these retrospectives are carried out with great fervor, teams often struggle on following up. This struggle is greater when teams begin to follow Agile.
Effective Retrospectives create learning teams and helps aid continuous process improvement.
In this talk, we'll walk you though a technique that applies continuous process improvement practices to help you many your retrospectives effective, easy to follow-up and measure your progress over the course of time.
In the 45 minutes of this interactive Talk, you will learn a very useful technique to interacting with teams and effectively communicating with "management" and other key internal stakeholders on the roadmap to continuous improvement.
Outline/structure of the Session
- UNDERSTAND AGILE RETROSPECTIVES
- Quick 5-minute Introduction
- What is Continuous Process Improvment?
- How can Continuous Process Improvement help Agile teams?
- What are retrospectives?
- How are Agile Retrospectives practiced and what is the gap?
- How is this different from Agile Retrospectives practiced today?
- How to gain mindshare for practicing Continuous Process Improvement in Agile teams
- How are goals important? What are they?
- How to plan for one?
- Learn the technique
- How to effectively practice this technique beyond your retrospectives?
- How can this technique benefit your organization?
- Understand how to plan for effective agile retrospectives
- Learn the tools and techniques to continuous improvement
- Understand "continuous process improvement" and its benefits
- Apply "continuous process improvement" practices to other aspects of Agile Project Management / practices
- Conduct Agile Retrospectives based on Continuous Improvement models
- Learn how to gain mindshare from key stakeholders to introduce this practice by presenting the business benefits of doing this
Product Owners, Scrum Masters / Project Managers, Portfolio Managers, Founders / CEOs, Developers
schedule Submitted 4 years ago
People who liked this proposal, also liked:
Vinodhini - Robotic Warehouses, Alien Domain, Offshore developers, Visionary customer : Saved by agileVinodhiniProject Manager / Agile CoachExilesoftThushara WijewardenaChief Project OfficerExilesoft
schedule 4 years agoSold Out!
Here is a case study of how agile outsourcing can be practically applied even when the business domain is very complex and alien to offshore teams.
The example is a project in which Exilesoft provided for a leading Norwegian producer of Robotic warehousing solutions. The project involved transforming their legacy application, produced using multiple suppliers and methods, into a newly cast application solution. This project also had its own share of typical challenges.
• Lacked definitive and reliable documentation,
• Domain knowledge was limited to a few very busy individuals,
• Development and redeployment could not interrupt attention to current customers,
• Complexity was high and design was fragmented, and
• Focus heavily invested on current product and customer support
These limitations along with the lack of understanding of agile methods strongly suggested the use of a method adaptive in nature, and not heavily vested in large inflexible legacy elements.
We commenced the engagement with two pivotal elements; client awareness (agile orientation) and a roadmap of committed involvement. To lay credibility this had to be backed up with proven result delivery in the very early stages. It allowed for flexible adaption, and the creation of an atmosphere that fostered client interest.
During this session, we will take the audience through a small video clipping of such a warehouse. We will elaborate how the customer and offshore developers worked together using agile in a highly integrated team collaboration model to achieve success within a very short time frame.
The session will cover the following key areas:
How such projects can be initiated
- What type of team model and contract type we used
- How we did the agile transformation with the customer
- How the roles were assigned between offshore and onshore team members
- To improve remote collaboration the tools and techniques we used
- Techniues learned to get teams up to speed with the new domain
- As we go along, the process changes we identified and implemented to make things work better.
- Agile engineering practices and team dynamics that helps in such situations