You might be wasting your time in ineffective daily meetings because you are asking the wrong questions. Could other questions give us a richer understanding of the current Sprint? The boring Daily Scrum I think the Daily Stand-up is one of the most misunderstood agile practices. As a coach, I get to see many teams …
The Scrum Master role is difficult to understand and execute well. It’s not a manager, it’s not a technical role, it’s not a boss. It’s a leader, facilitator and coach. Not all Scrum Masters are at this level; what about you? The Scrum Master is a very important role in Scrum. Like any important role, …
User Stories are the bridge between the customer and the development team. They are short, clear, written sentences which tell everyone what the system needs to do for the user. For the Agile practitioners, the user stories are known as one of the primary development artifacts for Scrum project teams. Those artifacts resume clearly the requirements …
Let’s say you start an agile project. You identify the requirements, write them down as user stories, define your releases, setup the infrastructure. Are you ready to start sprinting? Before we can answer, let’s try adding in more context. I see two different situations: 1. You have one team that will build an application starting …
Do We Need Architecture when Doing Agile or Lean? Read More »
“Once you stop learning, you start dying” Albert Einstein. I am a new member of Mozaic Works team and I am involved in marketing actions within the company. I learn new things and improve continuously my knowledge to face the day-to-day challenges. Learning is a continuous process and we can learn from anybody. My …
One of the courses our customers request the most is the Certified ScrumMaster training. This is an introductory to intermediate level class that teaches the skills needing to start leading a self-organizing team. After one of the sessions this year, we asked Xavier Quesada Allue, the trainer, to tell us a bit more about his …
After an initial romance with use cases, the agile community embraced user stories as its de facto standard for documenting requirements. You have probably seen them a lot by now and maybe even wrote a few: As a <user type> I want <action> So that <benefit> To make them more versatile, Mike Cohn introduced two additional …
