The Business Analyst is an agent of change
Business Analysis is a disciplined approach for introducing and managing change to organizations, whether they are for-profit businesses, governments, or non-profits. Business analysts work across all levels of an organization and may be involved in everything from defining strategy, to creating the enterprise architecture, to taking a leadership role by defining the goals and requirements for programs and projects or supporting continuous improvement in its technology and processes.
Business Analysis phases
At Clarus Group, we believe that the analysis and design phase of any project is the point where a projects success or failure can be measured. Clear, defined and documented requirements will limit the risk and chance of failure of any project. This can be achieved by many means, one way that we feel is extremely beneficial is called DFLSS.
Design for Lean Six Sigma (DFLSS)
Lean Six Sigma tries to fix broken processes that already exist. But what if there were a way to create higher quality processes at the design stage? A variant of Six Sigma, Design For Lean Six Sigma (DFLSS) is a methodology used to design from scratch or re-design a product or process to one that meets customer requirements and has an expected quality level of Six Sigma. DFLSS is about “getting it right the first time” instead of improving later (the focus of DMAIC Six Sigma). That’s the point where the cost of change is lowest and the ease of implementation is the highest. That’s where Lean is added to the mix, so it’s all the tools and techniques put together. A growing number of deployments are describing their efforts as DFLSS.
The Business Analyst role is a critical piece in the success of programs.
The Business Analyst has many different roles in the Software Development Life Cycle process. Business Analyst has the task of understanding business change needs, assessing the business impact of those changes, capturing, analyzing systems, documenting requirements and supporting the communication and delivery of requirements with relevant stakeholders. The BA role has expanded from traditional methodology roles to being highly engaged in more modern Agile processes to drive User Stories and product back logs through scrum process development.