Few Useful Facts about Agile Scrum

Did You Know that the name ‘Scrum’ began as a term in Rugby? The term basically describes a team that organise themselves and begins moving down the field together, as one. This analogy clearly shows why the term ‘scrum’ works so well in your team work too.

Change is the only constant in AGILE: I think this is the biggest challenge faced by every agile tester in their career. We cannot stop accepting change requests.

Agile can’t support large projects – Agile is based upon small, cross-functional teams that collaborate throughout the software lifecycle and is equally effective on small and larger multi-faceted systems. The trend of Agile teams to decompose work into smaller pieces is especially advantageous on sizeable projects.

Many Agile Scrum projects will involve learning as well as innovation and surprises. A major reccurring theme of Scrum will be to continuously inspect and adapt, for the success of projects that you and your team are working on.

Agile allows for fixed capacity projects –Certain frameworks in Agile require fixed capacity projects and others do not. When starting to help a Waterfall client grow in their Agile journey, we may recommend Iterative Waterfall or ScrumFall to start with rather than a direct transformation to Scrum. Iterative Waterfall and ScrumFall work well with fixed capacity projects. If the client desires to take full advantage of everything Agile can offer and eventually get to Scrum, or a scaled implementation, they must move to a variable capacity model and assign a full-time product owner to each team.

Agile is faster than Waterfall – Agile is less about delivering software faster, and more about delivering value faster. Which is worse, spending several iterations refining a feature with a customer to finally deliver what they really want or to deliver something faster, only to see it sit unused because we didn’t obtain feedback, and it didn’t match their expectations or didn’t adapt to a changing business landscape? Agile seems faster because there is less waste.

Agile projects are undisciplined and unstructured – Most Agile projects are more process-driven and synchronized than traditional Waterfall projects. Agile necessitates more discipline because the scope is continuously reviewed and modified from planning to production. Key stakeholders examine the advancement at set times and continuously provide feedback.

Lack of focused testing: Actual testing work gets a setback when the focus is shifted more on other work like documentation, generating test data, environment setup issues.

Accepting frequent builds: During sprint execution, builds are accepted too often, which has the high possibility of being a broken build as the code is changed and complied frequently.

The person responsible in an Agile Scrum for the product features is the ‘Product Owner’. They will create the to-do lists and prioritise these. They are therefore responsible for the return on investment.

Business Analysts are needed in Agile –  Like project managers, business analysts can take on a new title, such as Story Author. The Story Authors work very closely with the product owner to ensure user stories (requirements) are written in a way that most any developer can understand, and begin work on it without additional interaction.

It is a useful start to get Few such facts about the popular methodology.

Did You Know that the name ‘Scrum’ began as a term in Rugby? The term basically describes a team that organise themselves and begins moving down the field together, as ...
0 Comment

Leave a Comment

Your email address will not be published.