The purpose of this article is to explore feature files. Feature files are documents that contain those Gherkin scenarios & requirements – they can be very useful to teams working on BDD projects. Feature files may be a key deliverable for BAs.  Feature files are where BAs store requirements & can create the bridge between requirements and automated tests (more on that later).

Imagine that a business analyst has been assigned to write the requirements for a new system replacing the company’s legacy CRM (customer relationship management application).
After mapping out the as-is process at a high-level, the BA’s stress level starts to go up. “There are three complex modules in this system, and so many details about the as-is state that I still don’t understand! The legacy system barely has the original requirements documented, with plenty of change requests implemented later without proper documentation. How am I supposed to finish my deliverables on schedule and without mistakes given my limited knowledge of how the system being replaced works?”

A BA walks into an elevator, is joined by an executive, and suddenly the executive asks the BA, “So, what are you working on these days?” (Sounds like the start of a joke ...)  Most business analysts, due to their project success focus, think of requirements management when questioned about their work. So the BA responds by describing the features of a business solution that the BA is currently working. The BA seldom mentions the associated business benefits with the work (i.e. why the work is vital to the business). Unfortunately, the BA ignores the first rule of conversation: know your audience. The executive asking the question is more likely to understand and be interested in the business value provided by the work, rather than the solution features.

Agile Manifesto is a means to achieve the end objective through ‘best practices’ that crystallize into an approach that efficiently resolves the competitive stand-off. Thus the Manifesto is a subset of principles that provide a working framework to attain Agility. The following are high-impact Manifesto principles...

Estimating is one of the most controversial subjects in project management. There are some people who have turned the subject into a cryptic science involving esoteric techniques. Estimating is simply the process used to determine the amount of effort and cost required to implement a project, in part or in full. It is important to acknowledge that...

 In this article we look at some quality attributes that are particularly vital to explore when specifying requirements for embedded systems projects. Quality attributes for embedded systems can be much more complex and intertwined than those for other applications. Business software is generally used in an office where there’s not much variance in the environment. In contrast, the operating environment for embedded systems could involve temperature extremes, vibration, shock, and other factors that dictate specific quality considerations.

A requirement is “a condition or capability needed by a user to solve a problem or to achieve an objective” (AKA a goal). Thinking in terms of problems and goals thus is a core competence for the requirements engineer. But what in fact is a problem or a goal? This may seem to be a rather philosophical question. As requirements engineers we should be quite specific on this point as the problems and goals of our clients are the raison d’être for our work.

The experience age will force the business analyst, more so than ever, to be closer to business. The focus will have to move from how the IT landscape looks at the architectural level, to how it can be best utilised to provide the most compelling and efficient customer experience.  The success of business will now be determined by how well the customer journey and user experience has been translated to offer real and/or even perceived value for money through ‘virtual experience’.  It will be difficult for the business analyst to be a credible advisor to business without understanding the customer’s needs.

Prior to proceeding with a strategic project, project leadership needs to ensure that the project still:

• aligns with the direction of the business entity, and
• fits the needs of the targeted customer segment,
  as it did when the project was an initiative. This brief article starts at the inception of an initiative during Enterprise Analysis to the validation of a strategic project prior to kickoff. Note in this article, I include both the private and public sectors when I use the terms such as “business entity” and “customer segments.”

The role of design still puzzles many agile teams I work with. When should the design activities take place? Who should carry them out? How are design decisions best captured? This blog tries to answer the questions by discussing a user-centric, iterative, and collaborative design process for Scrum and Kanban teams.

An effective product roadmap is a must-have for any successful software development project. A roadmap helps the product manager define the trajectory of a product, communicate progress to stakeholders, visualize goals and justify changes to budget. Product roadmaps are where both strategy and tactics combine to help teams build better products.

So I came to a conclusion that I found interesting and want to share with the public: when doing this transition, the companies do not want to implement agile, they just want to run away from waterfall. And running away from waterfall can come in many shapes and forms, so the overall popular idea of comparing “waterfall” vs “agile” as two competing extremes is not conceptually correct.

There are some practices that can practically make our life much easier if we adopt them early in the project.  This fourth article of the series “ Business Analysts and Change Management - What we need to know” addresses the minimum that we - as Business Analysts - might need to know about change management, but this time at organizational level

The purpose of this article is to help YOU (fellow business analyst-perfectionist) to pass the CBAP V3 certification exam efficiently without overspending on prep materials. I wish there had been a CURRENT guide available for me when I stormed the CBAP fortress back in April 2017. After completing thorough online research, I found a few useful but outdated articles and other useful but disparate tips for how to pass the exam. But there was no comprehensive guide for passing the CBAP v3 exam on the first try.

Gherkin is a language used to write acceptance tests. BA's use Gherkin to specify how they want the system to behave in certain scenarios...  It’s a simple language. There are 10 key words (e.g. Given, When, Then). Because it’s a simple language, it’s understandable by the business. As well as being understandable by the business, Gherkin can be understood by an automation tool called Cucumber. That means Cucumber can interpret Gherkin and use it to drive automated tests. This links BA requirements to automated tests.