The majority of IT business analysts spend their careers in “reactive mode”. They are assigned to tasks like define the requirements for a new partner loyalty program, create user stories for an enhancement to a billing system, and go about delivering their artifacts.
Data-inspired analysts are those analysts who make a conscious decision to “go upstream” and find data to help their organizations identify the areas of value creation with the highest return on investment before jumping into “solution mode”.
An agile organization is characterized by having a comprehensive portfolio of optimized business process and business capability maps grouped by their role in value creation for the customers and support of the business strategy. These maps are linked to all the other disciplines such as finance, governance, resource management, talent management, and customer experience. Thus, Corporate IP can be securely delivered to the point of need.
I spent a lot of time in the past half-century doing software work: requirements, design, user experience, programming, testing, project management, writing documentation, process improvement leadership, writing 7 books and many articles, consulting, and training. Sure, there were some side trips along the way,.... But basically I’m a software guy. Over all that time, I’ve accumulated numerous insights about the software business. Here I offer 66 of those lessons. Perhaps you’ll find them as helpful as I have.
Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stakeholders have the following information available... But the more important question to have answer to and where the real business value is delivered in requirements life cycle management is answering the following questions:
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: