We are an ISTQB Approved Training Provider

(Click on the buttons below to list our current UK courses)

Resilia Cyber Resilience Courses Prince2 Agile Courses

ISTQB Certified Tester Courses ISTQB Agile Tester Courses

Scrum Master Courses Scrum Product Owner Courses

Practical Training

For the real world

Interested in learning Scrum?

As of 2015, Scrum is the most popular Agile framework in the world. So it's current, it's evolving and it works. At least it works when it's done right! That is what motivated us to start the IT Training Academy in the first place. As a bunch of scrum masters, testers and consultant agile coaches we encountered so many Agile teams who were under performing and doing Agile badly. After some root cause analysis we found that the reasons for this were firstly rooted in a lack of knowledge and training. Other reasons can exist on top of that, but if the foundations are poor then it's hard to move forward successfully. Our mission is to train you in Scrum in a practical way that leaves you with a solid understanding of how to implement the framework and why.

At a simple level, Scrum is a modern way to manage a project. In traditional project management a lot of time is spent gathering the details up front. Scrum starts with the premise that we don't really know the details of what we're building until we've built it. So we break our detailed work down into timed chunks called Sprints of up to 4 weeks of work. We plan the Sprint in detail and commit to delivering something potentially usuable at the end of that time boxed period. The benefit of this is that risk is reduced to the time period of the sprint. The alternative could have been to spend several months working on details, then several more months building, then several months testing and documenting only to discover at the end that it wasn't really what the customer wanted.

In Scrum, a representative of the customer, called a Product Owner, is part of the team. The team works closely together to create what the customer actually wants. This tight integration between customer and development team is key to the success of the project.

It is fairly easy to learn the basics of Scrum, but unless you understand why something is the way it is, you can end up stumbling along trying to be Agile but without the conviction of purpose that comes from a core understanding of why the Scrum framework works. We will teach you this core understanding using all of the experience we have gained as Scrum Masters in the real world.

4 Key Agile Values we teach

icon_one

Individuals and interactions

The Agile Manifestor lists this value first: "Individuals and interactions over processes and tools." They later emphasise that although they value both sets of things, they value "individuals and processes" more than "processes and tools". So what does this really mean to you in the real world?

read more
icon_two

Working software...

...over comprehensive documentation. There have been many studies of how users interact with software and many of them find that one of the last actions a user takes is to refer to the manual. So in terms of priority, the software should firstly work. Once it is then we can focus on more detailed documentation. Are there any pitfalls in comprehensively documenting a product?
read more

icon_three

Customer collaboration...

... over contract negotiation. Hmm, isn't this a little naieve? Don't we want to hammer out the details and clauses in case we get burned? How do we explain to the Procurement Department that we don't want to detail exactly what we will deliver to our customer. How is collaboration a viable alternative and how do we keep the legal department happy?
read more

icon_four

Responding to change...

...over following a plan. IT Projects have a very high failure rate and there is very good evidence showing that methodologies like Prince2 and PMP are no guarantees of success. Agile projects dramatically improve on that success. Let's learn to respond to change using Scrum.
read more

From the 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,...

 by  Mr Agile No Comments

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...

 by  Mr Agile No Comments

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...

 by  Mr Agile No Comments

A Product Owner without the power 🙁

I spoke to an organisation recently that was having trouble with a lack of clarity on backlog items. When I asked how their Product Owner (PO) dealt with that, I...

 by  Mr Agile No Comments

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...

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...

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,...

 by  Mr Agile No Comments

Roles

There are officially only 3 roles in Scrum:The Product Owner The Scum Master And The TeamThe Product Owner (PO) This role is a mixture of the traditional roles of the Project Manager, Product...

 by  Mr Agile No Comments

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...

 by  Mr Agile No Comments
view all