Notes to self

Your work is not just your work anymore. Probably it never was. Your work is also your life.  Probably the biggest part of your life. But your work is not you: it is also you. Having that in mind here are some notes for you my dear me: Sometimes you trust people too much. People … Continue reading Notes to self

Scrum Master Tip #7 – Small improvements for greater Scrum teams

Hi :) Christmas is gone but I have a gift to you, a rather small one, but as it happens with almost anything in life, great things come in small packages (cof cof cof) . I'll write about some small improvements I've done before that actually helped my teams a lot in finding their path … Continue reading Scrum Master Tip #7 – Small improvements for greater Scrum teams

Turning Dysfunctions into Actions – Fighting the 5 Dysfunctions of a Team

Hi All :) I just got this challenge today, from a colleague of mine, to convert my post   5 dysfunctions of a team  into something  positive we could show people without  scare them.  So rather than just posting on walls why we suck, the challenge is to post something that would make us think about … Continue reading Turning Dysfunctions into Actions – Fighting the 5 Dysfunctions of a Team

Creating your Scrum Cards – Free Template

Hi :) So after writing about how I prepare my templates (Creating your own Scrum Cards) for the team to write down User Stories, Bugs, Tasks and Improvements, I got some requests to make my template available. So here it is : US-Bugs-Task-ToPrint (excel format). Normally I print them using the coloured paper I want … Continue reading Creating your Scrum Cards – Free Template

Dealing with Legacy bugs in Scrum – THE BUGLOG!

Hi! After writing about Sprint backlogs - how you can create one and why it should be the big elephant in the room, I remembered we rarely see people talking about the nasty legacy bugs the scrum team gets during the sprint and how to fit them inside the sprint. First a disclaimer: when I … Continue reading Dealing with Legacy bugs in Scrum – THE BUGLOG!

Building your Sprint Backlog / Scrum Board

Hi :) Today a practical tip for building a Sprint Backlog aka Scrum Board. Why should we have a board? The board main function is to allow team to visualize remaining work (tracking) and facilitate daily synchronization (Re-plan). Everyday the team gets together, looks at the board (which contains the committed work) and the team … Continue reading Building your Sprint Backlog / Scrum Board

Leaders and Servants – Tips for the Scrum master

Scrum masters are not meant to lead (lead technically or in terms of business), they are meant to serve. And serving has different flavours. This 'epiphany' started with a 15 seconds chat with a fellow Scrum Master. - " Should you be a leader? "- I asked the scrum master - " Of course"- He … Continue reading Leaders and Servants – Tips for the Scrum master

The 7 Feet Under model – losing good people

It's time for me to finally publish and share my famous 7 Feet Under model. WARNING: this post contains strange things as Zombies, dirt, graves, stupidity, sarcasm and some other weird thoughts that may hirt the reader. enter at your own peril. The '7 Feet under model' is a simple visual summary of  my observations … Continue reading The 7 Feet Under model – losing good people

Engage your team – seeking and finding followers

Dear reader, How often when leading we use good examples to support us? How often when talking, while trying to explain something, we use that person (which we know it's already engaged) as an example to support to our case? It's human, we always seek for supporters. That's why we try to be surrounded by … Continue reading Engage your team – seeking and finding followers

Scrum Master TIP #6 – Retrospectives (2)

Hi there :)! Back in February I wrote this post about Retrospectives, giving hints on whom, when, why and  how to do it, plus some references for you to learn more about it. The thing is: I may not have focused something really really important: People HATE retrospectives, your job is to make them have … Continue reading Scrum Master TIP #6 – Retrospectives (2)

Perceptions – How important in a TEAM

    Wikipedia says that PERCEPTION is.. ..The organization, identification, and interpretation of sensory information in order to fabricate a mental representation through the process of transduction, which sensors in the body transform signals from the environment into encoded neural signals   And how important this is! … Perception simply defines the shape of the world for you. … Continue reading Perceptions – How important in a TEAM

Key indicators of Team happiness

Key indicators of team happiness was something that struck me the other day. Out of nothing, as always, something I heard while walking through the corridors and  that made this click on my head. Then I started observing some other things happening around me that also were a sign of team's happiness. There is more stuff … Continue reading Key indicators of Team happiness

Scrum Master TIP #5 – Retrospectives

  Retrospectives are probably the most important event for Teams, and probably the less valued. What I'm writing now is just a glimpse on retrospectives.. just a minor part of it. I truly advise you to read more about it (check bellow recommended book).   What are Retrospectives?   Retrospectives are the right time for … Continue reading Scrum Master TIP #5 – Retrospectives

From 1 to Many: Simple things about Teams.

How it started Today I was working out some slides I have on Agile & Scrum Intro... and I have this slide that describes what a Scrum Team is: 5 to 9 people Cross-functional (Programmers+ testers+ UX+..) Members should be full-time Self-organized Collaborative Autonomous, regarding how to achieve commitments Self-managed Stable – same team throughout the product sprints Negotiates commitment with … Continue reading From 1 to Many: Simple things about Teams.

Scrum Master Tip #4 : Daily Scrums

Two of the three  most powerful things about  scrum are  the Inspect and Adapt chances we have constantly. Although sometimes we can't see how important this 2 things are, they actually are the heart of scrum. It's really easy to misunderstand this 2 things with retrospective. Most people would think Inspection and adaptation is something … Continue reading Scrum Master Tip #4 : Daily Scrums

Scrum Master Tip #3 : Explain, Exemplify and Pratice

Being  a Scrum Master means a lot, if you do the right things. Being a Scrum Master is like being a leader: you won't drive the car, but you'll set on the passengers seat and you'll help the driver take the best route and be prepared for the risks of driving: without of course scaring … Continue reading Scrum Master Tip #3 : Explain, Exemplify and Pratice

Agilitypedia – User Stories

What are user stories A user story is simply something a user wants. A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. In short, user stories are very slim and high-level requirements artifacts. Why … Continue reading Agilitypedia – User Stories

Did you say Increments or Excrements?

I'm from the north of Portugal. That isn't good nor it is bad, but it means something. People from the north have a temper. Also they say exactly what they think and, they mean exactly they say. This may be a problem, specially now that I'm working on the south. Let me tell you about the … Continue reading Did you say Increments or Excrements?

Deliver? Piece of cake!

Today I had this marvelous experience, we called it Innovation day. A bunch of strangers from the same company (yes this may happen in big companies) stuck together in groups to implement an idea. We didn't knew the Idea, we read about it in a corporate tool, but the author was not available. Fortunately it … Continue reading Deliver? Piece of cake!

Scrum Master Tip #2 : Ready? Set, GO

It's a frequent thing for teams to say some things weren't delivered because Product backlog Items weren't properly defined. "The PO doesn't know what he wants". It doesn't mean that this is always true :) specially if the team is still in a Blaming stage. But it happens. If you work in a big company, … Continue reading Scrum Master Tip #2 : Ready? Set, GO