Why do we keep talking about the Enterprise Business Analyst (EBA)? Because it is quickly becoming the pivotal business/technology role of the future. The EBA is a business-driven strategic partner and integrator, an enabler of organizational change, and the driver of business success. As a strategic partner, the EBA often becomes an internal consultant – a business relationship manager at the top of the food chain of the BA profession.
Process Mapping is a group activity performed by teams of subject matter experts that gather to draw step-by-step diagrams to document how work is processed (see Figure 1). This invaluable tool is mostly used by consultants and business professionals to capture the current state of business operations in preparation for business improvement initiatives.
Having trouble extracting project requirements from your customer? Does your project client think they have already handed you all of their requirements and is asking why you aren’t starting to design the solution yet? Are they worried about eating up the project budget with useless planning when you could be starting the “real” work on the project?
There seems always to be questions surrounding aspects of the Product Owner role. Folks are always looking for clarity around what the PO should and should not be doing.
As a business, you are either efficient and effective, or you are not. It’s quite likely that there are things in your business environment you’d like to see work more smoothly, more efficiently. There are many reasons for poor processes and less productive business environments ranging from:
CLICK TO READ THE FULL WHITEPAPER - sponsored by PMI
Why are we the psychologists and the babysitters?
Often on airplanes I get asked, “So, what do you do?”
I am sure if you travel you get this one as well! Do any of you answer with “I am a therapist?”
For many of us, a new experience comes with varying degrees of anxiety and nervousness. This is particularly true if we have lingering doubts as to our ability to do what is being asked of us – even if such doubts have no basis. Moving from a job where you knew what to do like the “back of your hand” to one where the learning curve is steep is one of those nerve-wracking moments that test the mettle of any business analyst. Of course, the extent of your anxiety is minimized given your years of experience and success stories as a business analyst. That said, it is critical that as a business analyst entering a new role or job position you showcase confidence. Let your stakeholders know that you know that you can deliver the results they need even if you do not know their business like the “back of your hand”. Your work will speak for itself! It’s only a matter of time before you too become a domain expert.
If you’ve any experience in Agile approaches for software development, one of the common arguments surrounds documentation. Mostly it centers on software requirements, but it also extends to other forms of documentation, for example, design or user-centered documentation.
Everyone recognises the importance of good requirements writing. Good requirements must be written in such a way as to be clear and unambiguous to all readers. Explicit requirements require fewer review cycles to achieve approval.