Agile Daily Log

In this opportunity I want to share with you something that I learned some time ago and maybe you are already doing it: Daily logs at the moment we start with one team.

Personally I always find interesting all notes I take in the first 2 weeks I spend with the team. Not so long ago, I was reading one book about coaching and I really found interesting the format of those daily logs. I started to do it in that way and I really noticed some improve in my understanding of the whole picture after few days.

For this reason, I decide to take my first post to share this very powerful tool for any agile coach: Daily logs

Here one personal daily log:

Daily Personal Log (XX-NOV-XXX)


  • Jira overview
  • Daily stand-up invitation (Sean’s team)
  • Daily stand-up in OL team
  • 1-2-1 with Jose
  • Scrum of Scrum
  • Platform overview
  • Meet Scott & Guillaume: product overview.
  • First small meeting with Scott (PO) (1-2-1)

What went well

  • Integration is working fine
  • I am getting more information and a better picture of OL team
  • Business information is coming in my way
  • I guess issues start to pop-up

What went wrong

  • Review OL: PO need to work more in what he wants to see in the meeting if PO does not want to see all
  • Review OL: No way to show something with bugs. The team need to be sure that the product/feature/story is working
  • Retro OL: No good flagging issues and writing down AI to avoid them in the next sprint


  • how to show results from OL team (communication, estimation and QA)
  • designer and marketing resources seems to be working less of 100% in OL team (I need a confirmation of that)

Improvement Action

  • Bug should be part of stories (check with Cathy and in CoP meeting) – if not, why? –
    • 1 bug → 1 story (very complex/time consuming bugs)
    • severals bugs → 1 story (group of bug related or easy bugs)
  • OL need to start with BV
  • We have to be sure the team think at the Sprint goal (PO is include here)


  • QA activities (need to know Kathy plans/ideas)
  • Estimation issues (game or reading?)
  • Communication between team members (codeKata?)
  • Improve process → ballpoint game

Daily rating: 7/10


It seems to be very long, but it could take me around 10min/15min doing it. Personally, it is not too much time if I compare the benefit I get when I have to prepare the meeting with my line manager to explain my picture of the team after 1 or 2 weeks working in the company.

What do you think? As coach, are you doing something similar/different?

If you liked this, please subscribe you to my blog updates and get updates by email (I write between 2 and 5 articles per month). You will find the form here on the right side of the page.

Thank you,

Omar Bermudez


About the author

Omar is an agile practitioner and lover. Certified Scrum master. Agile Coach & Agile Leader. He believes it is important to continually be learning and growing. His dream is to be a lifelong learner; growing each day. He is also passionate about leadership development and seeing people reach their full potential. He is also a good husband & father (his wife says that time to times). He has a wonderful wife and 2 fantastic kids. In his free time, if he does not have any plan ahead, he tries to apply agile methodologies at the family level :). He enjoys a lot to travel with his family and discovers new places for them.