Some years ago 👴🏻, I wrote an article in a company tech blog about how we used Agile Methodologies in our development team.
I must say I was a bit obsessed with SCRUM events and roles at the time 🛐 but since then I have worked in many different teams and companies. Some were using Kanban, some said they were using SCRUM and others just weren't using any method at all 🤷🏿♀️.
So today I have a more clear picture in my head about what's really useful to integrate from Agile into a real-world development team process and what it's just "noise" 😣.
If you haven’t worked with SCRUM before, I recommend that you read the SCRUM Guide 📖 before continuing, it’s actually quite short and straightforward!
%[https://media.giphy.com/media/NFA61GS9qKZ68/giphy.gif]
-
💡 Introducing new ideas in a Grooming/Planning Meeting. It’s better to let Developers (from now on, Devs) do some analysis before doing a meeting where estimations will be asked. The Product Manager 👩🏼💻 (PM from now on) needs to assess which new features prioritize for the next Sprint depending on the effort needed, so it’s relevant that Devs do a proper analysis beforehand.
-
📄 Using Dailies as simple reports for PM. PM should be able to tell the status of the current tasks by looking at the Board. Dailies should focus on mentioning blockers and asking for help from other members of the team 👬. Avoid giving that help in this meeting: there’s nothing more unproductive and irritating for the rest of the Team than looking at a technical discussion between two Devs that they could have by themselves later on 🥱.
-
⛓ Forcing the team to follow all SCRUM rituals. For example, Sprint Review is a quite complex meeting because it should include Stakeholders so you need to coordinate with different team schedules 🗓. Sometimes it makes more sense if the PM meets those Stakeholders separately.
%[https://media.giphy.com/media/p3hZ9PbhVBO9gM6LoE/giphy.gif]
-
👩🏼💻 Having a dedicated PM for the team that acts always as a filter between Stakeholders and the Development Team. Devs cannot be productive if they are constantly asked about bugs or new features by many different people. At the same time, is useful that the PM has a complete picture 🗺 of the current project status, knowing about all bugs and features being proposed.
-
🛠 Actually using Jira: Jira is present in all the companies I have worked for, but almost nobody usually uses it effectively. Doing SCRUM Sprints and having a Jira Board doesn’t pay off if your team doesn’t measure their stats 📈 using the tools Jira provides. It's necessary to do retrospectives too if the team wants to improve its productivity.
-
🔧 Using Trello or other similar tools that are simpler than Jira. if you don't really want to measure your team performance or implement SCRUM completely, maybe you don’t really need Jira 🤷♂️. Trello makes creating a simple Kanban board very easy and it’s more intuitive to use for new users and people with 0 agile experience.
%[https://media.giphy.com/media/3ohs4xsq0oEhqC4why/giphy.gif]
Are you a full SCRUM follower? Or a Kanban lover? Let the world 🌍 know in the comments below!