Project Methodology

Preparation Execution Close

• Business Analysis

• Solution Approach

• Project Planning

• Sprints 1 - 999 • Transfer to Support• Wrap Up• Evaluate Solution

Performance

Project Phases

• Document business objectives and stakeholder requirements

• Bring stakeholders to agreement

• Identify solution approach

• Create a project plan to deliver solution

Roles:1. Business Analyst2. Consultant3. Technical Architect4. Project Manager (as needed)

“Understanding the requirements is critical to achieving the best solution.”

Project Preparation

What Why How

• What are you trying to accomplish?

• What are your current business processes?

• The business reasons for what you are trying to do

• Now that we understand the “What” and “Why”

• This is the start of the Solution Approach

Business Analysis

How do we get true requirements?

• Working with key users

• Interviews

• Focus Groups

• Observation

“We work to find the best solution that will fit the organization, taking into consideration its systems, processes, and people.”

Defining Requirements

Defining Requirements

Apply To Solution

ValidationElicitation

ReviewDefinition

12

34

5

Repeat

Requirements Definition Cycle

Jama Contour

• Trace requirements from creation through approval

• Add comments to each requirement for team review

• Collaborate and incorporate feedback

• Sign off individual requirements before proceeding with implementation

Requirements Tracking

1 2 3 4

Defining RequirementsSolution Approach

1Our Solution Team reviews the approved requirements to devise the appropriate Solution Approach

2The Solution Approach is presented. The customer team is asked to review it and sign off

3The approved Solution Approach is used to refine the Level of Effort Cost Estimate for the work. The customer project team will be asked to review it and sign off

4 After sign off, implementation begins

Solution Approval

ValidationElicitation

ReviewSolutions

12

34

5

Estimate

Solution ApproachSolution Approach

Tracking with Excel

• Requirements tracking from creation through approval

• Allows simple capture of requirements

• Allows for basic sign off of requirements

• After sign off, implementation begins

• A series of prioritized mini-projects called “Sprints”

• Detailed work tasks are created at the beginning of each sprint

• Collaborative team approach

• The Goal: Deliver business value during each and every sprint

Sprint Duration:

Project Execution

10-15days

Project Roles

Product Owner - Customer

Project Team – ArcherPoint, Customer, ISV(s)Consultant(s)Developer(s)Business Analyst

Project Manager

NPS Project Advocate

Account Manager

ArcherPoint Huddle

What is the Huddle?

Initial internal team meeting

Discuss Logistics – Hotels, office locations, dress code, airports

First round of sizing the User Stories

• Full Project Team – Client and ArcherPoint – is engaged (sometimes onsite)

• Introduce the client to Agile/Scrum Methodology and process

• Determine meeting frequency and optimal days/times for these to be setup• Standups • Sprint planning/reviews • Executive communication required outside of regular agile meetings

• Discussion about: • Desired Go Live date• Resources available • Length/number of sprints • Project Communication

• The first work effort (Sprint) is defined and the Project Execution phase is started

Project Planning - Kickoff

• Requirement – Ability to create and report standard financial statements

• User Story Template – As a <type of user>, I want <some desired outcome> so that <some reason>

• Example User Story – As an Account Manager, I want the ability to create a balance sheet, income statement, profit & loss statement, and cash flow statement so that I can report to the CFO our corporate financial standings

• Acceptance Criteria –1. All standard reports have been completed and reviewed2. Customer has been trained to run identified reports3. Customer has tested and confirmed validity of reports

Requirement vs. User Story

CA Agile/ Rally• Capture User Stories and Tasks

• Jointly track User Stories in process

• Manage priorities for all work tasks

• Sign off on completed User Stories

• Display overall project progress to all team members

Project Tracking

Documents that may be used throughout a project:

• Statement of Work• Requirements Deliverable• Sprint review• Status Update Report • Estimate to Actual • Change Request• Go Live Readiness Assessment• Go Live Checklist• Project Closure

Project Documentation

ArcherPoint SupportEasy-to-access Client Support Portal

Contact Support for:

✓General how-to and operational questions✓ Troubleshooting assistance✓Mission-critical support✓Compatibility questions✓ System installation issues✓ Training✓Requests for system changes✓Requests for enhanced services

Or visit us at www.ArcherPoint.com