45247 Views
27 Likes
0 Comments
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.
24738 Views
28 Likes
4 Comments

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.

17053 Views
10 Likes
0 Comments

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.”
21202 Views
14 Likes
0 Comments
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.
36709 Views
15 Likes
0 Comments
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.
16192 Views
24 Likes
1 Comments
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.
28517 Views
15 Likes
0 Comments
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
37598 Views
108 Likes
2 Comments
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.
104359 Views
87 Likes
3 Comments

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.


29884 Views
31 Likes
1 Comments
Business analysis is a broad discipline and we have a whole range of tools and techniques at our disposal. We may get involved within projects, but also outside of them. Many BA teams are actively seeking earlier engagement—when we are engaged prior to a project being initiated we can work with our stakeholders to ensure that the problem space is thoroughly understood. We can encourage stakeholders to think about many possible solution options, and can work with them to ensure that the option that is chosen is the best fit and has the best chance of delivering maximum benefit. Early engagement also helps us avoid the 'first solution trap'.
8977 Views
10 Likes
0 Comments
Ground rules are essential for any meeting. It may be what makes the meeting a success or failure. As a Business Analyst we are constantly organizing and facilitating meetings of various sizes to progress through the SDM (System Design Methodology) for a project. It is important that all sponsors and participants of the project understand what to expect from the upcoming meetings to be organized. Ground rules are generally discussed during the kickoff meeting, documented, and then displayed moving forward.
16739 Views
9 Likes
1 Comments

Scope creep (also known as feature creep, requirements creep, featuritis, and creeping featurism), however, refers to the uncontrolled growth of functionality that the team attempts to stuff into an already-full project box. It doesn’t all fit. The continuing churn and expansion of the requirements, coupled with inadequate prioritization, makes it difficult to deliver the most important functionality on schedule. This demand for ever-increasing functionality leads to delays, quality problems, and misdirected energy.  Scope creep is one of the most pervasive challenges of software development. 

 

44417 Views
11 Likes
0 Comments

Disbenefits are changes to on-going operating costs as a result of a project; they could be perceived as positive or negative. These disbenefits are included in defining the Total Cost of Ownership rather than a component of project cost, and is more of a focus for controllers due to its on-going nature rather than one time project savings and revenue.

35730 Views
40 Likes
1 Comments

Trying to secure a business analyst job interview in an area in which you don’t have prior experience can be a huge challenge. It’s common for recruiters and hiring managers to screen out applicants--no matter how accomplished they seem to be from their resumes--simply because the candidate’s job history doesn’t include work in the target industry...  But how do you get your foot in the door when so many recruiters and hiring managers tend to ignore applications from a candidate whose background doesn’t match the role they are trying to fill? The following tips may help.

20776 Views
13 Likes
0 Comments
When security requirements are considered at all during the system life cycle, they tend to be general lists of security features such as password protection, firewalls, virus detection tools, and the like. These are, in fact, not security requirements at all but rather implementation mechanisms that are intended to satisfy unstated requirements, such as authenticated access. As a result, security requirements that are specific to the system and that provide for protection of essential services and assets are often neglected. In addition, the attacker perspective is not considered, with the result that security requirements, when they exist, are likely to be incomplete. We believe that a systematic approach to security requirements engineering will help to avoid the problem of generic lists of features and to take into account the attacker perspective. Several approaches to security requirements engineering are described here and references are provided for additional material that can help you ensure that your products effectively meet security requirements.
Page 29 of 87First   Previous   24  25  26  27  28  [29]  30  31  32  33  Next   Last   

 



 




Copyright 2006-2025 by Modern Analyst Media LLC