Experienced and Agile http://www.tjbusch.com ...the way it should be Sat, 19 Aug 2017 00:31:13 +0000 en-US hourly 1 https://wordpress.org/?v=4.8.2 http://www.tjbusch.com/wp-content/uploads/2017/08/cropped-number-4--32x32.png Experienced and Agile http://www.tjbusch.com 32 32 Welcome to Understanding the Way It Should Be http://www.tjbusch.com/2017/06/12/understanding/ http://www.tjbusch.com/2017/06/12/understanding/#comments Mon, 12 Jun 2017 10:42:51 +0000 https://www.tjbusch.com/?p=1 Step 1 – Get Oriented As business analysts it’s our job to clarify the scope, requirements, and business objectives as quickly as possible. These terms are a bit ambiguous. Step 2 – Discover the Primary Business Objectives Uncovering and getting agreement on the business needs early in a project and before scope is defined is the quickest path forward to a successful project. Step 3 – Define Scope A clear and complete statement of scope provides your project team the go-forward concept to realize the business needs. Scope makes the business needs tangible and do-able. Step... Read Article →

The post Welcome to Understanding the Way It Should Be appeared first on Experienced and Agile.

]]>
Step 1 – Get Oriented

As business analysts it’s our job to clarify the scope, requirements, and business objectives as quickly as possible. These terms are a bit ambiguous.

Step 2 – Discover the Primary Business Objectives

Uncovering and getting agreement on the business needs early in a project and before scope is defined is the quickest path forward to a successful project.

Step 3 – Define Scope

A clear and complete statement of scope provides your project team the go-forward concept to realize the business needs. Scope makes the business needs tangible and do-able.

Step 4 – Define the Detailed Requirements

Detailed requirements provide your implementation team with the information they need to implement the solution. They make scope implementable.

Without clear, concise, and actionable detailed requirements, implementation teams often flounder and fail to connect the dots in such a way that delivers on the original business case for the project.

Creation of the Functional Design document (FDD) will describe the requirements is the actor, action, reason stance which provides what is needed along with a definition of done in one statement for each requirement. FDD supports the high level requirements stated in the project charter.

Step 5 – Support the Technical Implementation

On a typical project employing a business analyst, a significant part of the solution involves a technical implementation team building, customizing, and/or deploying software. The Technical Design Document (TDD) should support the FDD.

Step 6 – BA helps the Business Implement the Solution

Your technology team can deliver a beautiful shiny new solution that theoretically meets the business objectives, but if your business users don’t use it as intended and go back to business-as-usual, your project won’t have delivered on the original objectives. Business analysts are increasingly getting involved in this final phase of the project to support the business.

Step 7 – Assess Value Created by the Solution

Evaluating the actual progress made against the business objectives for the project to show the extent to which the original objectives have been fulfilled.

Communicating the results to the project sponsor, and if appropriate, to the project team and all members of the organization.

Suggesting follow-up projects and initiatives to fully realize the intended business objectives of the project or to solve new problems that are discovered while evaluating the impact of this project.

Source: Bridging the gap

 

The post Welcome to Understanding the Way It Should Be appeared first on Experienced and Agile.

]]>
http://www.tjbusch.com/2017/06/12/understanding/feed/ 1