This blog discusses topics relating to Agile and how agile concepts can be applied on software projects
A lot of people claim there’s a significant difference between DevOps and Agile. Agile is the description of a set of processes and principles, or a set of values guiding how to run software development. DevOps, on the other hand, refers to the umbrella vision of what was once disparate functions of an organization, from development, testing, to other operational functions and how the automation magic can redefine the business.
Read MoreAre you looking to put your BA skills to work in an Agile setting?
This post outlines a number of Agile certifications you could explore to prove you have the required knowledge required on Agile-based projects.
Read MoreThe 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 MoreThis article discusses 3 main approaches used by scrum teams to manage work and prevent scope creep, which other teams may learn from, whether organised as scrum teams or not.
Read MoreOne 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 MoreScrum 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 MoreOne 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 MoreThe 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 MoreIt’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 MoreHave you ever found yourself asking if requirements can ever be complete? Well, my answer is NO. Here's why...
Read MoreThis business analyst blog contains practical insights into business analysis, software testing and business process management. I will be sharing business analyst tips, CBAP Certification tips, lessons learnt and insights into all the things I've learnt during my BA career.
