Business analysts have a potentially long list of responsibilities and deliverables. Finding the time within a project to include all of the best practices can often be a challenge, and some important techniques, deliverables, and responsibilities are often neglected or ignored simply because there isn’t enough time available. This includes such things as requirements traceability, stakeholder analysis, reports analysis, impact assessments, and handoffs to other project team members. These are often sacrificed for the sake of creating the perfect requirements document, use cases, or diagrams and models. I’d like to focus this article on one of these often neglected work items – handoffs to other project team members.
The term “requirements traceability” refers to the ability to map requirements back to business goals and objectives, and also to map requirements forward to test cases, business processes, software, training materials, and more. The concept is quite simple, really – it’s a way to tie everything together from start to finish, and make sure that end products align with originating goals and objectives.
Looking back across my career, I’ve had the opportunity to work with many different and unique businesses, operating in various industries. I’ve also worked on a wide variety of projects, from new application development, to solution selection, to solution integration and implementation. One thing that I’ve learned during that time is that for all the differences and uniqueness, most businesses and projects have much more in common than most people expect. Sure, the culture of a business or industry might be different, and work being performed might be completely unique, but many of the underlying needs, attitudes, approaches, personalities, and behaviours that you encounter from one project or business to another are fundamentally the same.
The Object Management Group (OMG) is defining a new standard for decision modeling: Decision Model and Notation (DMN). If you aren't familiar with the OMG, they are an organization whose goal is to develop standards by reviewing and refining commonalities between existing models and notation.
As a business analyst, I am regularly looking for new tools and techniques to add to my toolkit. I’d like to tell you about one such technique. It’s definitely a useful technique for business analysts, but could equally be useful for project managers or other types of consultants.
This year's Building Business Capability (BBC) conference was held in Las Vegas, after years in Florida. If you've never been to Las Vegas, it's quite an experience. Personally, I think that three or four days in Vegas are more than enough to visit all the hotels, see the sights, and take in a show or two. Next year, the BBC will return to Fort Lauderdale again – a much more peaceful and relaxing location.
As portable devices continue to get smaller and more powerful, they are increasingly becoming more suitable for taking over everyday office duties. Over the past year, I've found myself using my tablet and smartphone more for tasks that I had previously allocated to my laptop.
I recall how much effort it took to study for my Certified Business Analysis Professional (CBAP) exam two years ago, so when I went to the Building Business Capability Conference in October 2012, I was very interested in attending Kevin Brennan’s session about the upcoming BABOK v3. Plenty of questions had crossed my mind, including:
Topics: Business Analysis