Comic Agilé

Comic Agilé no. 101 - The Background of RTEs (reshare) Remember that an RTE is more of a Scrum Master than a Project/Program Manager. An RTE’s most valuable task is doing for the ART what the Scrum Master does for the team, namely whatever needed for it to continuously improve itself, facilitate that systemic impediments are addressed, etc. But, then again, why not just spread the RTE competency between a group of Scrum Masters? #agile #scaledagileframework #releasetrainengineer #comicagile

Comic Agilé no. 326 - Burned Out Testers Doing Test-Driven Development can help you shift-left on testing activities. #agile #testing #tester #qa #qualityassurance #comicagile

Comic Agilé no. 326 - Burned Out Tester Doing Test-Driven Development can help you shift-left on testing activities. #agile #testing #qa #qualityassurance #comicagile

Comic Agilé writer Luxshan describes how to take on the challenging people role in an agile context through stances: https://lnkd.in/dfKqr2ct #agile #linemanager #middlemanagement #peoplemanager #stances

Comic Agilé no. 325 - Fixing the Bug Remember that a PBI is not really done before meeting the DoD and its quality criteria. #agile #testing #test #qa #comicagile

Comic Agilé no. 95 - Little's Law (reshare) According to Little's Law, the delivery lead time of stories increases if we increase our Work in Progress (WIP) without a corresponding increase in throughput (e.g., by breaking down stories into smaller, more manageable tasks). Conversely, reducing WIP can lead to shorter lead times, as the team can focus on fewer tasks simultaneously. In the context of Sprint Planning, while WIP is timeboxed by the sprint itself, planning fewer or smaller stories can help ensure smoother flow and quicker completion of individual stories, improving overall delivery efficiency, and enabling faster feedback. #agile #littleslaw #sprintplanning #comicagile

Comic Agilé no. 31 - Retrospective (reshare) According to the Scrum Guide, the Sprint Retrospective is where the team inspects itself and creates a plan for how to improve in the next sprint. So, where the Sprint Review is for inspecting the Increment (the ‘done’ PBIs), the Retrospective is for improving the way the team works in order to deliver the work. In order to have useful Retrospectives, there must be trust between the team members, so they can live up to the Scrum values of openness and respect. This trust is built over time between the members of the Scrum team, and the Retrospective is a venue where this trust leads to the team members expressing themselves freely in order to improve the team. Therefore, if people external to the team (such as Managers) wish to participate, we as Scrum Masters and Agile Coaches need 1) understand why this person wants to participate and 2) bring the suggestion to the team, so they can take the decision. One risk of having external stakeholders at Retrospectives is that the focus can change from inspecting the team process into focusing on refining the work to be delivered. So, unless there are some hidden advantages to the outcome of the session of having external people participate, avoid it. It’s the team’s session. #agile #scrum #retrospective #comicagile

Comic Agilé no. 166 - Using Scrum to Become Agile (reshare) Adopting Scrum will not magically turn your organisation into an agile one. Just like a scale only shows your current status on a weight loss journey, the scale, itself, will not make you lose weight—changing your eating habits and exercising will. The root causes of why your PBIs get blocked are often good indicators of the systemic changes that your organisation needs to make to be agile. E.g., if a team’s stories get blocked because they need the Data Warehouse team to make a database change, or because a security clearance is needed from the InfoSec department, building up these competencies within the Scrum Team (and taking the needed political battles on a Management level to allow it) is a way of “losing weight”. #agile #scrum #weightloss #scale #weight #comicagile

Comic Agilé no. 210 - Conflicts in the Team (reshare) Managers should support Scrum Masters in handling team conflicts by mentoring, coaching and sharing their own experiences. Healthy teams have constructive conflicts, as long as they remain respectful. Scrum Masters must embrace conflict, trusting that the team will navigate it. Take a facilitator role—ensure everyone is heard, address personal attacks and guide the team toward resolution. If no agreement emerges naturally, help the team decide collectively (e.g., by voting). Encouraging open discussions after conflicts strengthens Courage, Openness and Respect within the team. #agile #conflictmanagement #comicagile

Comic Agilé no. 293 - Holacracy (reshare) Don’t create a hierarchy between the circles; it’ll make it wholly crazy! #holacracy #agile #organisationaldesign #comicagile