Blog

Load Testing

The ISTQB define load testing as: A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g. numbers of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system Hmmm, sounds a little like…

Read more

Severity versus Priority

Many parts of testing require a pedantic view of words and the ISTQB Certified Tester syllabus is very specific on the meaning of words. Severity is defined as the extent to which a defect can affect the software. In order to use a common language for testing it is very…

Read more

Individuals & Interactions…

This if the first of the 4 value statements from the Agile Manifesto. "Individuals and interactions over processes and tools" With each of the 4 values the original authors emphasise that they value both sides, but they value the values on the left more. So what does that mean in…

Read more

Working software…

The second value listed in the Agile Manifesto is: Woking software over comprehensive documentation Notice the use of the word "comprehensive" above. The authors are not saying don't do any documentation at all. They are not even saying not to do comprehensive documentation. I think they are saying that where…

Read more

Responding to change over following a plan

This is the 4th set of values from the Agile Manifesto. Responding to change is a pretty good definition of "Agile". Most Project Managers will be used to following a plan, whether they use Prince2, adhere to the PMBOK or any other framework, it generally comes down to planning the…

Read more

Artifacts

I never liked the word Artifact and in the UK we are more used to the concept of Deliverables, but is a burndown chart a deliverable? Not to my mind, so let's stick with the Scrum terminology. An artifact in Scrum is one of the following: The Product Backlog The…

Read more

Roles

There are officially only 3 roles in Scrum: The Product Owner The Scum Master And The Team The Product Owner (PO) This role is a mixture of the traditional roles of the Project Manager, Product Manager and the Customer. As far as the Team is concerned, the PO is the…

Read more

Leading by example

I started as a Scrum Master in a team that had already been using Scrum for over a year. At the first standup I introduced myself and then listened as each team member shared what they had been working on, what they were going to work on that day and…

Read more

Building Bridges with the Customer

The Scrum Guide defines the role of the product owner as “responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.” So this is very much open to interpreation. Personally I see…

Read more

Sprint Goals

When I first arrive in an organisation, whether it's to be a Scrum Master, a Product Owner or an Agile Coach, one of the questions I ask is what is your current Sprint's Goal? I often get a slightly confused look, then a stumbled answer along the lines of "to…

Read more

Spikes

Spikes are an invention of Extreme Programming (XP). Scrum was derived partly from XP. Spikes are a special type of story that is used to drive out risk and uncertainty in a user story. You may want to think of it as a research item or a prototype item. In…

Read more

Going along even if you disagree?

The scenario: You're a Scrum Master, you're in a sprint planning meeting and another team member raises an issue. You disagree that it's an issue and don't think we should allocate extra time to deal with it. Your colleague disagrees vehemently and you suddenly find yourself in a showdown. How…

Read more

Story Estimating

Estimation in Agile is a relative estimation process. It's a guess, a place to start from. This can be a difficult concept for management to grasp, where facts are preferred so they can hold us to account. This comes from a lack of understanding of the development process and how…

Read more