|Why Every Job Seeker Should Have a Personal Website, And What It Should Include|
Business Analyst Community & Resources | Modern Analyst
RSS feeds for Business Analyst Community & Resources | Modern Analyst
How Will It Work? The Future How Viewpoint...
The intention of these viewpoints is to make it easier to see and understand the real business problem. This article focuses on the fourth viewpoint, the Future-How, which looks at the solution to the business problem. It does this by assessing alternatives, and then choosing the best solution to that real business problem.
Detailed Requirements for User Interfaces and Reports
For business analysts working in an environment where there is a gap between SMEs and the delivery of an IT-based solution for business needs, requirements are documented to bridge that gap. You are reading this because you are a business analyst responsible for documenting detailed requirements and, in the case of this article, business needs involving one or more user interfaces (UIs) or reports. The objective of this article is to answer the question, “How much detail is necessary?” Spoiler alert – quite a bit. This is to avoid, as much as possible, a BA having to go back to a SME when designers or developers have business-level questions about a UI or report. Or worse – designers or developers not asking questions. Instead, making assumptions about what the business needs and proceeding to deliver the solution based on those assumptions.
The Problems Addressed by Business Rules
Business rules cover a very broad space. Across the entire space, however, you can be sure about one central idea – business logic should not be buried in procedural programming languages. Call it rule independence. Why is rule independence important to you? Because rules entangled in procedural code won’t ever be agile. Rules change all the time – and in a digital world the pace of change is always accelerating. How you can stay on top of it is the central question in business agility.
Human Face to Enterprise Architecture
If we look at the previously proposed process end to end, it starts with the customer journey. The journey is mapped to the internal business processes, systems, and data sources. For both the customer facing and internal parts of the journey user stories are created to document the gaps between the as-is and to-be states - effectively form the backlog for the change. For each story, acceptance criteria are prepared in a way that enforces the expected behaviour in the system. Ideally, those should be the scenarios that are likely to appear on the real life journeys and not the hypothetical future scenarios. These scenarios when implemented and tested feed back to the journey and underlying layers changing them as the new functionality is introduced.
Is there a role for a business analyst in an Agile environment?
This question has been asked several times before, and various answers have been advanced to settle this matter. A short answer is ‘Yes’. But, unfortunately, this answer is not good enough to the ‘naysayers’, who think a business analyst has no place in Agile teams. To answer this question in a long way, we have to take the bull by its horns and talk about the elephant in the room. This article is an attempt to contribute to this ongoing debate. Whether you agree with me or not (as I tackle this elephant in the room), the truth is - this argument is apposite and has to be had.
Integrative Thinking (Mental Models for Business Analysts, Part II)
Learning about mental models and how to apply them to their work is one of the best investments for business analysts interested in achieving the level of deep thinking that leads to better outcomes for their projects and organizations. The first article in this series described what mental models are and talked about the first mental model covered, second order thinking. In this second installment we discuss another mental model that that can help business analysts become better problem solvers: integrative thinking.
9 Types Of Requirements Documents: What They Mean And Who Writes Them
Requirements documents are used to communicate the aims of a project in a clear, concise way to ensure all stakeholders are on the same page. When we talk about a requirements document we are often referring to a Business Requirements Document - or a BRD. But as well as a BRD, there are 9 other types of requirements documents that a business may want to use while pushing a project through its stages of completion. The type of format to be used depends on the result of the project itself, whether it’s a product, service or system, and the particular requirements it has.
What’s Missing from Agile?
John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information technology the last thing to be concerned with, not the first.
Six Estimation Safety Tips
Estimation is a chronically thorny issue for software practitioners. Most people need to prepare estimates for the work they do, but in our industry we don’t do a great job of estimation. In this article I offer six safety tips to keep in mind as you prepare estimates for your project and for your individual work... These six safety tips might not help you create estimates that all of your customers, managers, and coworkers will dance to, but at least they will help you and your team hear the same music.
Requirements Gathering meets Accessibility Needs
The ethics behind accessibility is possibly not something you have considered before. I think many would categorise an accessibility tool as something that; ‘makes life easier’, for a disabled user. However, what we should be taking into account when designing new digital platforms is how to make sure that every single user has the same experience. This is actually a very key point as we are not even specifically talking about disabilities here. Have you considered mobile users vs web? IOS vs Windows? Online vs Offline? These are all possible different users of your system and all deserve the same experience. It may well be that a lot of these points are non-functional requirements that come later in the development, but if you make sure you are considering them at the start, you can save yourself a lot of time and effort in the future.
Managing Data-Specific Business Needs Using a Data Dictionary
The previous article in this series discussed ensuring that high-level requirements (HLRs), within the context of an IT-based project, were properly high level. The remainder of articles in the series will look at detail requirements and the need for them to be sufficiently detailed. The objective of this article is to demonstrate how a data dictionary (DD) can be used as a tool for capturing the appropriate level of detail representing data-specific business needs.
Trips-R-You Web-based Flight Booking Case Study
The purpose of the Trips-R-You Flight Booking Case Study is to provide an integrated, end-to-end set of requirement examples. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. This case study, and associated artefacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detail Requirements. Only functional requirements are addressed, and only within the context of a project chartered to deliver an IT-based solution.
Build Requirements Around Real Journeys
Let us look at it from a different angle now and derive the requirements out of the customer journeys. It is impossible to introduce a change... if the change is big and you try to implement it in one go. This is the reason we tend to break any solution into smaller components. Each solution component should be small and independent enough to be changed individually in a controlled manner. So that eventually we will compose a new experience out of them. Pretty much like using a set of Lego blocks.
Domain Expertise and the Business Analyst: How Vital Is It?
The question of how essential domain expertise is to a business analyst is a recurring debate in the BA community. One school of thought maintains that domain knowledge is not critical. A skilled BA, the thinking goes, can walk into nearly any project situation and do an effective job of exploring requirements, relying on previous experience and a rich tool kit of requirements techniques. The counterargument avers that an analyst who has deep subject matter knowledge can be far more effective than a more general practitioner. I have experienced both situations, from inside a company as a regular employee and from the outside as a consultant. This article offers some thoughts about when domain knowledge is valuable, when it’s essential, when it’s not necessary, and when it can actually pose a risk.
Second-Order Thinking (Mental Models for Business Analysts, Part I)
Learning about mental models and how to apply them to their work is one of the best investments for business analysts interested in achieving the level of deep thinking that leads to better outcomes for their projects and organizations.
Experience Driven Development: Design for real people
For the business, it means they not only need to understand the problem the customers are trying to solve - they need to understand that problem in a context and design a full end-to-end experience of solving it. Some people call this process “human-centered design”, some - just using common sense when designing stuff.
Promises, Promises: Negotiating Achievable Commitments
Successful projects—and successful relationships—are based on realistic commitments, not on fantasies and empty promises. This article, adapted from the book Practical Project Initiation, presents several ways to improve your ability to make, and keep, achievable commitments... Unfulfilled promises ultimately lead to unhappy people and unsuccessful projects. Strive to build a realistic commitment ethic in your team—and in yourself.
What happens when the BA and UX worlds collide?
Are you a Business Analyst (BA) wondering what User Experience (UX) Design is all about and how your involvement in a design project is likely to impact your usual role? If so, I’ve also been pondering the same question for some time.
Be the bird in your projects to become a better BA
The reason why top performing business analysts tend to be so effective in complex projects, even when their domain knowledge is limited, is because of their ability to see things from a higher angle and with more nuanced colors.
Requirements Review Challenges
If someone said you could only perform a single quality practice on a software project, what would you choose? I’d pick peer reviews of requirements, which I believe are the highest-leverage quality practice we have available today. In a peer review, someone other than the author of a work product examines the product for quality problems and improvement opportunities. Reviewing requirements is a powerful technique. Use them to identify ambiguous or unverifiable requirements, find requirements that aren’t sufficiently detailed yet, spot conflicts between requirements, and reveal numerous other problems.
How BAs Fit into Projects and Development
As the business analyst (BA) role continues to evolve, the responsibilities continue to expand. One of the best ways for a business analyst to add value to a project is to understand the processes involved in both the project life cycle (PLC) and the software development life cycle (SDLC). Contrary to popular belief, the two life cycles are independent of one another, however, it's best that they are aligned.
Ninety Percent Done
The fact that software projects and tasks are reported to be “90 percent done” for a long time has become something of an industry joke. (A related joke states that the first half of a software project consumes the first 90 percent of the resources, and the second half consumes the other 90 percent of the resources.) This well-intentioned but misleading status tracking makes it difficult to judge when a body of work will truly be completed so you can ship the next product release to your customers. Here are several typical causes of “90 percent done” syndrome and a few possible cures.
Top 10 Most Common Reasons People Fail the CBAP Exam
Many professionals approach us after being unsuccessful in CBAP so we thought of doing some analysis to come up with the most common reasons of failure in CBAP. There are many articles and blogs giving tips on how to pass the CBAP exam but on a first search, I didn't find any article explaining why people fail in CBAP. This will definitely help the CBAP aspirants to make sure that they don't repeat the mistakes.
Making Requirements Reusable
Reuse is an eternal grail for those who seek increased software productivity. Reusing requirements can increase productivity, improve quality, and lead to greater consistency between related systems. Reuse is not free, though. It presents its own risks, both with regard to reusing existing items and to creating items with good reuse potential. It might take more effort to create high-quality reusable requirements than to write requirements you intend to use only on the current project. In this article we describe some approaches an organization could take to maximize the reuse potential of its requirements.
Keeping High-Level Requirements High-Level
The objective of this article is to provide business analysts with guidelines for distinguishing between high-level requirements (HLRs) and detail requirements (in IIBA® BABOK® V3 terms – Stakeholder requirements and Solution requirements respectively).
Systems Analyst Jobs
Listed by State – Updated Daily
Powered by FirstRSS Plugin