Sprints are more than just pushing code—they're micro-innovation "projects": build and deliver something valuable, gather data, inspect and adapt. If you do it right, your stakeholders won't get enough!
But how can you as a Developer 💪help💪 or 💥hurt💥 the Sprint?
Hurt:
- 💥 Be limited: Architects are for Architecture, Testers are for testing, and you are for writing code? No way! Own all the work. If you're a code typist, AI will gladly take your job!
- 💥 Be waiting: Waiting for someone to tell you what to do? Waiting to raise an issue? That’s wasting time. You’re part of an expert team—solve problems together.
- 💥 Be scared: Playing it safe? Afraid to try something new or adjust the plan? How are you going to learn if you never take a risk?
Help:
- 💪 Be focused: Always know why your work is valuable. Align everything you do with that—every. single. day.
- 💪 Be learning: Critical, Constructive and Pragmatic (CCP). Hold yourself and others accountable to doing better together.
- 💪 Be replaceable: From tracking progress to sharing knowledge, set your team up to continue without you. If the team succeeds, you succeed.
Now you're ready to break the limit!
Be sure to check out my card game: Mode/Switch
Top comments (0)