Strategies for Implementing Aras Innovator

29
aras.com Copyright © 2013 Aras. All Rights Reserved. DOMORE ACE 2013

description

 

Transcript of Strategies for Implementing Aras Innovator

Page 1: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved.

DOMOREA C E 2 0 1 3

Page 2: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved.

A C E 2 0 1 3

Strategies for Implementing Aras Innovator

Learn how to effectively plan and implement Aras Innovator using best practices and methods proven by Aras to make your deployment a success.

Page 3: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 3

Agenda

Our Approach Aras Methodology Getting Started Getting it Done What to watch for Final thoughts

Page 4: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 4

Our Approach

Use modern Iterative design principles Agile, Rational Unified Process, Agile Unified Process, DaD Utilize the components that work for you

Use a small win strategy Define a problem, solve it, move on to the next Shoot for a release in 90-120 days

Page 5: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 5

Guiding Principles

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Collaboration over contract negotiation

Responding to change over following a plan

Agile Manifesto2001

Page 6: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 6

Iterative Approach

Inception Elaboration Construction Transition

Envision &

Plan

Incrementally define and build a consumable solution

Release &

Rollout

Page 7: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 7

Why Iterative Development

It favors working solutions over detailed documentation that has little value to end users

It provides the mechanism to continually refine requirements

It is proven to deliver a solutions that meet the needs of real end users.

Traditional systems, like Waterfall, tend to fix requirements at the start of a project This very rarely produces the desired result

Page 8: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 8

Compare Approaches

ValueDriven

Requirements(Scope)

DateResources(Cost)

PlanDriven

Requirements(Scope)

Resources(Cost)

Date

Estimated

Fixed

Traditional Approaches

Iterative Approaches

Page 9: Strategies for Implementing Aras Innovator

BREAKING DOWN YOUR PROJECTMANAGEABLE PHASES

Page 10: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 10

The Big PictureDisciplines

Business Modeling

Requirements

Analysis & Design

Implementation

Test

Deployment

ConfigurationManagement

Project Management

Phases

Inception Elaboration Construction Transition

I1 E1 E2 C1 C2 C3 T1 T2

Milestones

Page 11: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 11

Inception PhaseDecide what to do

Primary Objectives: Scope the system adequately Validate initial costing and budget estimates

Activities Establish Business Case and high level Requirements High level Use Cases Project Plan and Initial Risk Assessment

Milestones: Stakeholder concurrence on scope, cost, and risk Initial requirements defined (not a lot of detail) Achieve Project Plan concurrence Plan is realistic Business case makes sense

Slide 11

Page 12: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 12

Elaboration PhasePlan the details Primary Objectives:

Improve requirements and validate End to End skeleton

Activities Requirements elaboration & Use Cases Design Workshops Visual Prototyping User validation

Milestones: Use Cases identified and 80% complete Requirements are understood & documented Project Plan refined, cost & risk are managed Detailed plans for iterations are in place

Slide 12

Page 13: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 13

Construction PhaseBuild it

Primary Objectives: Build the system end to end

Activities Visual prototypes Behavioral Prototypes Data Migration Unit test

Milestones: Solution is acceptable to deploy Project Plan refined, cost & risk are managed Additional Iterations are planned

Slide 13

Page 14: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 14

Transition Phase Deploy it

Primary Objectives: Move the system to production Training & fine tuning

Activities End user training Documentation Full system test (production environment)

Milestones: Solution & documentation is ready to deploy Stakeholders are near ready to deploy System is functional in production

Slide 14

Page 15: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 15

An Innovator Project

Slide 15

Disciplines ActivitiesInception

Initial Parts Change Parts Change Interface T1 T2Install Test Environment

Train Project TeamKickoff Meeting

High Level RequirementsDiscovery workshop(s)

SoWProject Charter & Solution Overview

High Level Use CasesRequirements Workshops

Requirements Document(s)Gap analysis

Use Case DevelopmentSolution Design Doc

Functional specs for customizationsScreen Mockups

Visual PrototypesImport Users

Configure ItemsConfigure Forms

Configure WorkflowsConfigure Roles & Permissions

Behavioral PrototypesDevelop Data Migration

Interface developmentDevelop Customizations

Prepare Test PlanUnit Test

Full System TestPrepare User Docs

Develop User TrainingDeliver User Training

Build & Deploy Prod EnvProduction Data Migration

PackagingMigrate Dev-QA-ProdChange Management

Initial Project PlanInitial Risk Analysis

Project Planning & Design Review

Milestones

TIME

PhasesElaboration Construction Transition

Project Startup

Business Modeling

Requirements

Project Management

Analysis & Design

Implementation

Test

Deployment

Configuration Management

Page 16: Strategies for Implementing Aras Innovator

GETTING STARTED

Page 17: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 17

Getting Started Develop a Project Charter

Lets everyone know what you will do and will not do Defines a goal and an endpoint to measure success Should list the business problems that will be addressed

Organize your team Develop a Plan

Lets resources know what is expected of them Defines how the functionality will be delivered

Get Trained The team needs to understand Aras Innovator

Review the standard Aras Innovator Solutions Required for effective gap analysis

Slide 17

Page 18: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 18

How to approach itDivide and Conquer Divide implementation into phases

Preferably phases that provide business values and can be deployed independently

Build a plan for each phase Choose goals for each phase and make sure you address

items with importance or high risk sooner Divide phases by related business processes

Build high level use cases for these business processes Its OK if use cases overlap

Break down high level use cases Detail each use case from a user perspective These will likely be developed iteratively

Slide 18

Page 19: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 19

ResourcesWho do you needRole ResponsibilityProject Manager • Direct Implementation resources

• Manage project schedules• Track Status• Resolve conflicts and issues

Business Process Owner(s) • Provide project priorities and objectives• Direct participation of resources• Resolve business process issues

Subject Matter Experts • Communicate current process• Provide information details• Support user community during rollout

I.T. System Support • Support site infrastructure• Extract legacy data• Provide technical expertise

Technical Resources • Configure application• Develop customizations• Provide technical expertise

Slide 19

Page 20: Strategies for Implementing Aras Innovator

GETTING IT DONE

Page 21: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 21

Getting It DoneElaboration - The key points

Make sure you achieve concurrence on requirements This provides mutual understanding and prevents individual

interpretations of the project Document use cases and requirements

These will be used to provide context to the team Will be leveraged later in the project for other activities

Validate this with SMEs and end users Don’t underestimate this

Focus on high value activities Make sure that you address risk

Slide 21

Page 22: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 22

Getting It DoneConstruction - The key points

Visual Prototypes This is just building things in Aras Innovator Used to solicit user feedback May cause you to revisit use cases and specifications Don’t worry about getting it 100% right

Behavioral Prototype Adds automation to the Visual Prototype May introduce changes to the Visual prototype Includes building interfaces and integrations

Provide regular releases for user feedback

Slide 22

Page 23: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 23

Regular Releases

Development Release for User validation

Production Release

Page 24: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 24

Getting It DoneTransition - The key points Test Plans

These are based on use cases Testing and Validation

Unit testing is important for managing iterations CRPs are a good method for user validation Full system test

Training Don’t underestimate the time it takes to develop materials

or train end users Production Cutover

Plan, Plan, Plan, - there will be external influences

Slide 24

Page 25: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 25

Making Iterations WorkThings to think about

Work is done in a serial fashion but you don’t need to finalize a discipline before moving on to the next Address some requirements, analyze, develop and go back

Iterations should be planned according to risk Higher priority risks first

Near term iterations are planned in more detail Longer term items may change in scope, etc Doesn’t mean that longer term items are not planned

Slide 25

Page 26: Strategies for Implementing Aras Innovator

BEST PRACTICES

Page 27: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 27

Implementation Best Practices Develop iteratively

Its always best to know all the requirements up front but this is not reality Don’t spend an inordinate amount of time upfront on requirements and design

w/o user validation Model a little, test a little & repeat

Manage Requirements Always keep in mind the objectives set by the users

Model Visually Use diagrams and mock ups This is what end users relate to

Constantly Verify Quality Always make user testing a major part of the project

Monitor Change Insure changes are synchronized and verified constantly Use a managed process for implementing iterations

It’s Really Easy once you get the hang of itSlide 27

Page 28: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 28

How Things Get Sideways

Lack of requirements understanding or agreement on requirements

Lack of understanding of the standard Aras Innovator solutions

Lack of Training Underestimating the impact of change Biting off too much!

Slide 28

Page 29: Strategies for Implementing Aras Innovator

aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 29

Final ThoughtsDos and Don’ts

DO Get Trained Create visual prototypes and get user validation before

developing any method code Develop accurate Use Cases and keep them up to date Look for “Small Wins” that provide business value

DON’T Spend a significant amount of time developing specs w/o

prototyping the solution Worry about not getting 100% of the detailed

requirements up front - because you won’t!

Slide 29