The 2018 Guide To Pursuing A Full Agile Software Lifecycle

The 2018 Guide To Pursuing A Full Agile Software Lifecycle

The term, Agile, in software development refers to a group of development processes based on solving problems through collaboration across teams. It is a framework that encourages developers to work together, stay accountable, and constantly seek improvements. Using Agile is a way to compete in a world of constant demand. 

Read More

Agile Business Analyst Certification: The Professional Scrum Master I (PSM I) Certification From Scrum.org

Agile Business Analyst Certification: The Professional Scrum Master I (PSM I) Certification From Scrum.org

One of the quickest ways to prove your competency as an agile business analyst is getting certified. Though having experience on agile teams is valuable, it’s also worthwhile going the extra mile to formalise that experience by getting certified. Certification is also a great path for those without experience on agile teams to get their feet wet.

Read More

8 Characteristics Of Scrum Teams BAs Should Know About

8 Characteristics Of Scrum Teams BAs Should Know About

Scrum is one of the most widely used frameworks aligned to Agile and is adopted extensively across software development teams.

This article highlights some characteristics of scrum teams you should be aware of if you are a business analyst and you find yourself working as part of a scrum team:

Read More

Techniques Every Agile BA Should Know About - Part 1

Techniques Every Agile BA Should Know About - Part 1

One of the main characteristics of Agile Business Analysis is the use of “lightweight” techniques. The very nature of Agile analysis which emphasizes customer collaboration, working software, individuals and interactions, and responding quickly to change implies that certain techniques fit the bill more than others do.

Read More

Qualities of an Agile Business Analyst

Qualities of an Agile Business Analyst

The Agile software development methodology is based on lean principles and accommodates changing demands within a short space of time; it is based on the premise that requirements will always evolve and encourages teams to adapt to changes instead of attempting to specify the system completely ahead of development. This post is a follow-up to Waterfall to Agile: The Role of BAs in Agile Projects and contains a list of the qualities every BA should have (or plan to have) in order to go “Agile”.

Read More

Waterfall to Agile: The Role of BAs in Agile Projects

Waterfall to Agile: The Role of BAs in Agile Projects

It’s much easier to see the usefulness of BAs in traditional waterfall development environments where requirements have to be clearly defined in Requirements Specification Documents before system development can begin. In Agile environments however, users and developers are expected to sit in the same room and agree on what will be developed, with little emphasis on documentation. Is the BA role in Agile software development being threatened? 

Read More