They create the Business User Stories and help set the priorities of those User Stories.

They help define the Acceptance Criteria for the Architect Team to map the requirements to Design Acceptance Scenarios

The Business Domain Knowledge is communicated to the Architect Team by the Subject Matter Experts.

All Business terms used by the Stakeholders and Subject Matter Experts are captured by the Lexicon Master and added to the initiative’s Lexicon of Terms.

This dictionary of business phrases, words and concepts are maintained using a define daily maintenance process by the Lexicon Master.

The Lexicon of Terms creates the design and development naming convention for all technology architecture. Changes to the Ubiquitous Language trigger a change in the architecture, design and developed code.

This role is a non-speaking member of the Daily Scrum Stand Up Meetings.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

This Agile Role is the bridge between the Business Team and the Technology Teams.

The Product Owner manages Client expectations by communicating, in business speak, information about the progress and issues of the Agile Sprints to the Business Team.

This role also communicate, in technology speak, to the Technology Teams the expectations of the Business Team.

The Product Owner participates in the Daily Scrum Meetings to maintain awareness of daily issues that may impact delivery.

The Product Owner is the key role to manage and communicate issues to the Business Team and to the Technology Teams before they become problems or disasters.

This role facilitates, with the help of the Scrum Master and representatives from the Business and Technology Teams, successful resolution of potential problems.

This role is a non-speaking member of the Daily Scrum Stand Up Meetings.

All resolution details are scheduled as an “Off-line” meeting, with the relevant Team Members. after the Stand up meeting by the Scrum Master.

They help provide understanding of the Client’s business model to the Architecture team.

The Business Domain Model is created with the knowledge gained by the Business Analysts interactions with the Business Stakeholders.

This role is ultimately responsible for all aspects of the Client’s initiative and works closely with the Business drivers to managing changing requirements throughout the engagement.

This team member helps the Business Analysts and Architect team to thoroughly understand the success criteria of the engagement.

The Program Manager ensure changing requirements are addressed and communicated to the Project Managers for disseminated to the key team roles.

The Scrum Master runs the Daily Stand Up Meetings and acts as the primary facilitator in resolving all team member defines blocks.

This role works with the Product Owner with Client expectation management.

The Sprint’s additional Backlog assignments and Burn-down rate of scheduled deliverables are managed and monitored by the Scrum Master.

The Scrum Master ensures that the Continuous Integration (CI) processes and Sprint Deployments are successful for each Development Sprint iteration.

A tight working relationship exists between the Architect and Development Teams along with QA and the Network Team.

The Business Domain Entities defined will help create the Technology Domain Entities used to map the Business to the Technology solutions.

The entities are part of the business processes that must be understood by all as they apply to the initiative success criteria.

Locations where the business processes are implemented will be discussed and details presented for understanding.

The organization’s roles and responsibilities of people involved with the initiative and the changes related to the technology solutions will be evaluated and communicated for impact on the daily business operations.

All time sensitive Business Events will be evaluated for proper scheduling of delivery and deployment of the technology solutions.

Proper scheduling of initiative deliverables will help support the strategic goals. These actions are carefully aimed to maximize the initiative’s success criteria.

This Lexicon of Terms creates a common understanding of the relationships that the Entities has with the Business Domain.

A complete understanding of the Business Processes that act on Business Domain Entity Model will be understood and communicated as Domain Knowledge to the Technology Teams.

Terms of these processes will be added to the Lexicon of Terms and uses as naming conventions during the Architecture and Design processes.

Geographical locations that will be impacted by the deployed solutions will be discussed and implications evaluated.

The Business Organizational work flow models must be evaluated for the impact on the daily activities of the work force.

Consideration must be discussed for the business impact for the deployment of the delivered technology solution to the business environment to the work flow.

The success criteria should be driven by the Business Event Cycles that would benefit from timely Technology releases to the marketplace.

A strategic business plan should define the Business Objectives to help define the priorities of the defined Business User Stories for the initiative.

This Lexicon of Terms creates a common understanding of the relationships that the Entities has with the Business Domain.

A complete understanding of the Business Processes that act on Business Domain Entity Model will be understood and communicated as Domain Knowledge to the Technology Teams.

Terms of these processes will be added to the Lexicon of Terms and uses as naming conventions during the Architecture and Design processes.

Geographical locations that will be impacted by the deployed solutions will be discussed and implications evaluated.

The Business Organizational work flow models must be evaluated for the impact on the daily activities of the work force.

Consideration must be discussed for the business impact for the deployment of the delivered technology solution to the business environment to the work flow.

The success criteria should be driven by the Business Event Cycles that would benefit from timely Technology releases to the marketplace.

A strategic business plan should define the Business Objectives to help define the priorities of the defined Business User Stories for the initiative.