Gary Law and his colleague, Lance Elston, are Business Analysis Managers with Insperity, co-managing a group of 20 business analysts (BAs), each of whom serves as a liaison between Insperity’s 17 line-of-business managers/product owners and the company’s teams of application developers. It’s the BAs’ job to help ensure that the end-products from all development teams align with the product owners’ business requirements.
Law and Elston recognized that their BAs, while well-versed in technology and Insperity’s agile development practices, needed a deeper understanding of business processes. As a result, they instituted a program called, Putting the Business Back in Business Analysis. “We’re an agile group, so our BAs were meeting once or twice a week with business owners gathering their requirements. However, they didn’t know exactly which business processes were executed on a daily basis, so the BAs did not have the insight they needed, which made it more difficult to build software,” says Mr. Law.
According to Mr. Law, Insperity’s informal workflow environment sometimes produced a fragmented grasp of business processes. “Our teams would often have a partial understanding of touch points and interfaces in their heads.” Business process modeling was often limited to drawings on dry-erase boards, and documentation was informal and ad hoc.