Regularly celebrating team successes 🎉
Starfish Retrospective Examples
Keep Doing
- 0 0
- Maintaining clear and open channels of communication 📢0 0
- Adhering to agile sprint cycles efficiently 🔄0 0
- Conducting thorough code reviews for quality assurance ✔️0 0
- Practicing continuous integration and deployment for smoother releases 🚀0 0
- Encouraging team members to take regular breaks for well-being ☕0 0
Less Of
- Overloading the team with tasks beyond capacity 📉0 0
- Long and unstructured meetings 🕗0 0
- Micromanaging team members' tasks 🕵️0 0
- Relying on email for urgent communication 📧0 0
- Neglecting documentation or code comments 📄0 0
- Jumping too quickly to new technologies without proper evaluation 🔍0 0
More Of
- Pair programming sessions to enhance knowledge sharing 👥0 0
- Feedback sessions from end-users to understand their needs better 🗣️0 0
- Time for professional development and learning 📚0 0
- Cross-functional team collaborations 🤝0 0
- Regular updates on project progress and obstacles 📊0 0
- Incorporating design thinking in problem-solving sessions 🎨0 0
Stop Doing
- Skipping retrospectives or other important meetings ❌0 0
- Ignoring team feedback and concerns 😕0 0
- Postponing regular maintenance and technical debt repayment 💳0 0
- Using outdated or inefficient tools and processes 🛠️0 0
- Working in silos without seeking input from other team members 🏝️0 0
- Accepting unrealistic deadlines without proper negotiation ⏳0 0
Start Doing
- Implementing a buddy system for new team members 👫0 0
- Using time tracking tools to improve project estimates ⏱️0 0
- Regular health checks for critical systems 🔍0 0
- Scheduling brainstorming sessions for innovation 💡0 0
- Establishing clear guidelines for remote work and communication 📡0 0
- Creating a knowledge base for internal best practices and learnings 📖0 0
- Keep Doing
What practices are currently working well and should be continued? This includes any actions or processes that are contributing positively to the team's workflow and success.
- Less Of
What practices are somewhat beneficial but are being overdone or are not as effective as they could be? These are activities that should be reduced but not eliminated entirely.
- More Of
What practices are beneficial but underutilized? These are activities that the team should increase to improve their workflow or outcomes.
- Stop Doing
What practices are currently a hindrance or are no longer serving the team well? These are activities that should be ceased to improve team performance and efficiency.
- Start Doing
What new practices should the team implement? This includes new ideas or actions that have not been tried before but could potentially benefit the team.
Don't have an account? Try EasyRetro for FREE now!
