Posts in Business Analyst Blog Category

business requirements gathering training

What is a Requirements Management Plan?

Requirements Management is a systematic approach to: Finding, eliciting, organizing, documenting and managing requirements Establishing and maintaining agreement between the customer or user and the project team on the changing requirements The Requirements Plan contents are as follows: Types of requirements…

What is a sprint retrospective meeting

The purpose of the sprint retrospective is to have a lessons learned session.  The team should review the stories in the sprint and discuss what has been completed and what has not been completed in the sprint.  They should also…

Sprint Planning Meeting- Scrum Master

The Scrum Master is responsible for ensuring the tasks are completed before the Sprint starts: Define the sprint lengths- usually 2 weeks to 30 day period Present the stories and acceptance test criteria- The Product Owner leads the team through the…

Sprint Planning Meeting

At the beginning of each Sprint, the Product Owner conducts a Sprint Planning Meeting with the team.  The purpose is to review the product backlog items and identify the priority for the items that should be included in the upcoming…

Project Life Cycle using data and uml

Building a Context Diagram

The Context Diagram describes the scope of the data requirements for a project.  It shows the highest level activity or function and the external objects that interact with it.  Business Analysts should know how to create the context diagram when…

Project Life Cycle

Building a Logical Data Model

Data Modeling is a skill that a Business Analyst should think about developing.  If not building the diagram, at least the BA should know how to read and validate them.  There are two types of models that are important for…

Scrum Artifacts

Below is a list of primary artifacts that are created during an Agile Project.  For more information register for Pierson’s Agile Training for BAs & Product Owners class. Product Backlogs Product Backlog Items Sprint Backlog Sprint Task Sprint Burndown Chart…

Agile Project Characteristics

Priority is the satisfy the customer Deliver functionality frequently Iterations are 2 – 4 weeks Use techniques such as time-boxing & dedicated teams Collaboration with business users throughout the project Face-to-face conversations Working software is primary measure of success Attention…

Agile Requirements Analysis

It is necessary to define the project initiation before beginning an agile project.  Define the project upfront.  The proper planning is needed to be successful. Identify the Epics and User Stories Gather the initial product backlog from the stakeholders- list of…

Business Requirements Categories

Business requirements are typically classified into three business requirements categories.  The categories are functional requirements, non-functional requirements and design constraints.  The definition of these categories are: Functional Requirements: Describe the system features or things the system must do to support…