The relentless pace of technological progress drives businesses to work on increasingly more complex projects. With this increased complexity comes new challenges and roadblocks that business analysts must learn to overcome.Read More
Business Analysts play a pertinent role in determining what functionality a system should or should not have. If you can ask these questions of every requirement, the implemented solution will have a higher possibility of acceptance:
1. Vision: How will the system work to fulfill this requirement?
2. Scope: Is this requirement within the scope of what the project is intended to accomplish?
3. Engage: Have I discussed this requirement with ALL relevant stakeholders?
4. Model: Have I presented this requirement in a manner that is easy for ALL to understand?
5. Simplify: Is this requirement necessary and practical?Read More
Governance seems to be one of those frightening words that threaten to stop an Agile transformation effort dead in its tracks. I’ve been hearing it whispered, and even screamed once or twice, quite a lot recently. There’s no big surprise here. As the big corporations and Government agencies get increasingly fascinated by frameworks like Scrum, they are mandating their IT departments to “Go agile” and then, sooner or later…governance!Read More
In preparing a business case, the business analyst is often required to conduct some measure of cost analysis. When highlighting the benefits associated with an initiative, it is extremely important to also indicate the costs that will go along with implementing the initiative. Information regarding costs is particularly important in making go or no-go decisions when deciding which projects to implement. The business analyst should work with the project manager to identify these costs and arrive at realistic estimates.Read More
Managing stakeholder expectations is essential to business projects' success. If you know ahead what stakeholders “expect” the system to do, you can advise them of this well ahead of time to avoid disappointments further down the road.Read More
According to Stephen Ward & Chris Chapman in their piece, Stakeholders and uncertainty management in projects, “Stakeholders are a major source of uncertainty in projects and this uncertainty stems from whom these stakeholders are, their motives, and how they can influence a project.”
It is this uncertainty that constitutes risks to the project. BAs should relate with other project stakeholders to overcome this uncertainty by improving their ability to convince stakeholders to see things their way, thereby influencing the course of the project.Read More
BAs can learn a lot from UXers, that much is certain. But perhaps the most valuable thing the two disciplines can learn from each other is working together. Both roles have the same ultimate aim—to produce a product that has business value and meets users’ needs. The approaches may differ but are far from conflicting: BAs create value by delivering good features and functions, UXers by delivering good experiences. Guest Post by Cassandra NajiRead More
This post is a compilation of websites with resources that can boost your technical skills, and help you become better at work. If yours is one of those organizations that have cut back on training programs; you've been assigned to a new project or perhaps it's just out of pure interest in the world of techies, you’ll certainly find these websites useful.Read More
It’s best to select a small number of key attributes and establish a system that allows us to add more requirements attributes as we go along, depending on the nature of the project and which attributes are deemed necessary.Read More
As development practices change, so do the reasons why we write requirements and the level of detail we go into with Requirements Specification documents. Even seasoned business analysts have at one point or the other asked themselves, “What level of detail is enough?”. The answer to this seemingly simple question is surprisingly complex and is inseparably intertwined with the reason why we write requirements in the first place: so that they can be read, understood, and implemented.Read More
The main goal of all business analysts is to uncover unknown risks and requirements during the requirement discovery phase. But as many business analysts will surely attest to, sooner or later, the problem of scope creep inevitably arises, unless one takes concrete steps to prevent it.Read More
This post comprises a list of free training that business analysts can use to gain the knowledge and experience of what to do when practising business analysis within the context of business intelligence.Read More
The list below comprises a list of free business analysis training courses that can help you hit the ground running whenever you practice business analysis within the Agile context. They are as follows:Read More
It's that time of the year again and here is a list of the most popular 2016 posts, as determined by BAL readers. This list is based on the number of page views received by each post.
Here it goes:Read More
We make hundreds if not thousands of decisions every day. Some more important, others less so. With each decision we make, we shape our future and possibly, come closer to the attainment of our goals. One of the most effective ways to increase productivity and make better choices during requirements elicitation is by organizing facilitated sessions among stakeholders.Read More
Documentation of software requirements should not be seen as optional, but a necessity. While the level of detail may vary depending on the approach adopted, be it Agile or Waterfall, it’s important to keep in mind why documentation is needed in the first place, before one goes too far in the wrong direction.Read More
Needs Analysis is similar to business analysis especially in the sense that it is used to determine the needs of the business, and is centred on understanding the issues and opportunities faced by the business with the objective of finding resolutions, defining approaches to resolving issues and exploiting opportunities. In summary, it’s about:
Regardless of size and complexity, the goal of the business case remains the same: to convince decision-makers to approve a proposal. Here are some of the things a business analyst must keep in mind for a winning business case. Guest post by Shuba KathikeyanRead More
From analysing data and preparing deliverables to supporting stakeholders through other stages of the solution development lifecycle, the role of the BA is certainly key to successful projects. The end of the elicitation event does not signify the end of business analysis activities, but the beginning of the BA’s involvement in other aspects of the project.Read More