ย 
Search

5 fundamental steps before you can call yourself agile

Let's talk about #software development. Here are five health checks you can quickly run on your teams before you call them agile.


Most #product companies nowadays have small agile teams (hopefully even empowered product teams). But still, I hear here and there that project management is used for running those teams. It does not match or make sense. Five things to check:


๐Ÿ”† 1. Are #standups really for team sharing and not for reporting someone? Standups should never be about reporting. You can quickly test it :-)


๐Ÿ”† 2. Is it clear to everyone that during planning / grooming / or other similar meetings, nobody yet knows which development tasks they are personally going to develop later on? It's crucial that everyone is present in the discussion and wouldn't have a mindset of "this does not concern me". Sharing product- and code knowledge inside a small team reduces risks and improves quality.



๐Ÿ”† 3. Do you have a (sprint) #backlog in priority order? And developers always take the following task with the highest priority? More often than not, priorities are pretty straightforward, and the next thing to do should be the one with the highest possible #businessimpact.


๐Ÿ”† 4. And, of course - do you do #rapid#releasing? Every commit is released, and nothing stays on someone's laptop for days? I could never go back to releasing weekly or even less often. It slows teamwork and product growth.


๐Ÿ”† 5. Is the code review done as soon as possible? Preferably on the same day? Even if you use continuous deployment and releasing is done before code review. Any agreements in the team regarding that?


Yes, those are five fundamental steps, yet some teams are not following those. I sincerely hope that you are ๐Ÿ˜ป

5 views0 comments

Recent Posts

See All
ย