In scrum, and in many Agile frameworks, the term ‘T-shaped’ refers to the skills of the members of the team. The team members have a skill or skills that they specialise in, and then they have other skills that are competent in but are not specialists. In a typical development team, the majority of team … Read more
Having been a Scrum Master for different teams in different companies, I have seen what works and what doesn’t. The characteristics of a good product owner are the ability to understand their product, and to explain the product strategy and vision to their stakeholders, and to the scrum team. They should also be able to … Read more
The Daily Scrum is a short meeting, held at the same time and place every day for the developers of the Scrum Team. The reason for having the Daily Scrum meeting is to: In the Daily Scrum meeting, the team discusses their progress toward the sprint goal, reviews the Sprint Backlog to see if changes … Read more
Timeboxing is restricting a meeting, a task or activity to a specific timeframe – a specific start and end time. The advantage of doing this is to focus for a specific period of time, document the outcome, and then move on. This puts pressure on the team to focus and produce an outcome, a decision … Read more
According to the Scrum Guide, the daily scrum is a chance for the developers in the team to inspect and adapt. They inspect their progress towards the sprint goal and adapt the sprint backlog if needed. In the daily scrum, the product owner is an observer and listener, and not necessarily an active participant. While … Read more
For a new scrum master, the first few months can be challenging – there’s a whole team (or teams) looking to you for guidance and help, a new group of stakeholders, and the opportunity to finally do things your way. The opportunity is there in many ways, not only in the way the team works, … Read more
What is an information radiator in Agile? Simply put, it is a screen or board in a prominent place that provides information – i.e. radiates information. This information can be status information – alerts, monitoring graphs, build status including unit test results, automated tests, SLA status, or other information on upcoming events, experiments the team … Read more
Agile is not a programming language. Agile is not even a framework. Agile can best be described as a mindset or a set of principles to help developers produce the work in an efficient and sustainable way. The principles of Agile, described in the Agile Manfesto, guide the way in which to structure your development … Read more
I’ve worked in places where the word fragile was used to describe Agile, which was often followed by a smile or a laugh, despite no one using the term fragile having any solid experience with XP, Kanban or Scrum. When there was no direction for the project, requirements were not clear, or when things were … Read more
Which Agile workflow tool is right for your team? This article describes the top ten tools for 2021.
