TL;DR
How to improve me to be ready and prepared for dailies avoiding boring behavior that wasn’t helping my team. Remember, this is not a rule to do something. This is a personal thing that helped me. It’ll help you, It won’t. Do not take this as a rule for you.
THE MOST COMMON OF MYSELF AT DAILIES
Have you ever “forgot” everything that you did yesterday in the Daily meeting? I had this problem as well, let’s see how we can fix this.
It shouldn’t be hard to get yourself lost during dailies meeting. When it´s your time to explain what you did or what you are doing, how many times you forget? Got a blank? As time goes, I realized that this is normal behavior, mostly for new coworkers.
How many people got this same issue and how they passed by it? Thinking about learning in public, I started to share my way inside the company to improve this. So, why not share with everyone I can?
START TO LISTEN
Our cofounder, @rafaturk says a thing pretty interesting: on the daily meeting you need to think that is not only what you did yesterday. You need to sell your work for your team. Must say how that thing as simple as it, it will help your team in many ways it can. Mainly if this is directly connected with the sales team's needs.
WHAT I DID
First of all, to understand what I did, you need to understand how we work at Entria. We have milestones by weeks, and every day of this week we have dailies to follow how is going the sprint. A basic scrum from any company. On these dailies, we advise our co-workers, right from the start, to say if they are blocked and how to help. The other things flow naturally.
The first thing that I did was to keep a list of everything that I was working on, some times with a bit more of detail, and everything that I’ve done
Started by month, splitting by weeks based on our milestones, and these weeks split by days. Below is an example of a “daily remembering notes":
OCTOBER
MILESTONE 05–09 - GitHub link of milestone
TRACK ISSUES
- www.github.com/daniloab/fullstack-playground/issues/1
- www.github.com/daniloab/fullstack-playground/issues/2
DOING
- X thing at Y feature www.github.com/daniloab/fullstack-playground/issues/1
07/10
- it was decided on daily that the new use case it will fix on issue #2
start to implement the new feature to handle onboarding of clients by institutional site
06/10
- improve deploy with GitHub actions
- improve the thumbor of files
- finished new front-end XYZ
for next daily (07/10): bring to the team how to resolve the new use case appeared on new front-end XYZ
05/10
- improve some awesome feature
- fixed the sandwich icon in the navbar
- fix responsive thing on the institutional website
CONCLUSION
First, the link of a milestone to create an easy way to access what you need to do and remember.
Second, I put a track of new issues that I create while the sprint is happening. In this way, I can control what needs to do, is doing and the new use cases created from this.
Third, a simple topic with what I´m doing.
By last the days and what I did in each one. Look for 06/10 I simulated a new use case found. So, I like to note and bring at new daily to discuss with the team what we will do.
END
You could think that this is not a big deal, but you should sell the work you are doing. People that sell better have more chances to get a promotion, grow up, and scale. Also, this may sound a little coach, or even obvious. However, within scope, the obvious for one may not be obvious for another. Tell me if you do something similar or if it is different share it with us, remember: learn in public.
Top comments (0)