![]() Read: " Frontend Developer RoadMap 2020" 4. The team should discuss and create risk mitigation techniques around such scenarios, the successful risk mitigation technique can also be used in other projects. The unavailability of suitable prebuilt software modules or components, changed or extended requirements, sudden eviction of crucial team members whichever is the reason that can extend the development time, cost and reduce business value for customers can be termed as pirates i.e. Unclear documentation, insufficient requirement gathering, insufficient team members, unavailable resources, or vague development path or targets could be the obstacles as rocks. ![]() Read: " Backend Developer Roadmap for 2020" 2. Team members, skills, gathered requirements, or reusable code that’s propelling the team forward. The tickets will be categorized into the following perspectives: 1. ![]() Now the team members can submit their tickets on the whiteboard with sticky notes or a digital team collaboration board. The sailboat’s base should be half in water half outside of it which represents well-balanced team. In sailboat retrospective meeting the agile coach and product owner should draw a sailboat, wind, rocks, pirates and anchor. To curb this issue the team members should create a rule with mutual consent that no one will blame each other and present defending arguments. Sailboat Retrospective TechniqueĪlthough retrospectives are essential for teams they can turn out to become a quarrel hence the facilitator must be careful while conducting this meeting. Retrospectives are an integral part of running sprints and sailboat retrospective technique is one such technique where sailboat represents team, wind or air represents things that are propelling the sailboat forward, the anchor represents the things that are slowing them down, rocks are obstacles and pirates are risks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |