aras.comCopyright © 2013 Aras. All Rights Reserved.DOMOREA C E 2 0 1 3
aras.comCopyright © 2013 Aras. All Rights Reserved.A C E 2 0 1 3Strategies for ImplementingAras InnovatorLearn how to effe...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 3Agenda Our Approach Aras Methodology Getting Started Gettin...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 4Our Approach Use modern Iterative design principles Agile, Ra...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 5Guiding Principles Individuals and interactions over processes...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 6Iterative ApproachInception Elaboration Construction Transition...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 7Why Iterative Development It favors working solutions over det...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 8Compare ApproachesValueDrivenRequirements(Scope)DateResources(C...
BREAKING DOWN YOUR PROJECTMANAGEABLE PHASES
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 10The Big PictureDisciplinesBusiness ModelingRequirementsAnalysi...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 11Inception PhaseDecide what to do Primary Objectives: Scope t...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 12Elaboration PhasePlan the details Primary Objectives: Improv...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 13Construction PhaseBuild it Primary Objectives: Build the sys...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 14Transition PhaseDeploy it Primary Objectives: Move the syste...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 15An Innovator ProjectSlide 15Disciplines ActivitiesInceptionIni...
GETTING STARTED
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 17Getting Started Develop a Project Charter Lets everyone know...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 18How to approach itDivide and Conquer Divide implementation in...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 19ResourcesWho do you needRole ResponsibilityProject Manager • D...
GETTING IT DONE
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 21Getting It DoneElaboration - The key points Make sure you ach...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 22Getting It DoneConstruction - The key points Visual Prototype...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 23Regular ReleasesDevelopment Release for User validationProduct...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 24Getting It DoneTransition - The key points Test Plans These ...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 25Making Iterations WorkThings to think about Work is done in a...
BEST PRACTICES
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 27Implementation Best Practices Develop iteratively Its always...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 28How Things Get Sideways Lack of requirements understanding or...
aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 29Final ThoughtsDos and Don’ts DO Get Trained Create visual p...
Upcoming SlideShare
Loading in …5
×

Strategies for Implementing Aras Innovator

1,269 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,269
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
50
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Strategies for Implementing Aras Innovator

  1. 1. aras.comCopyright © 2013 Aras. All Rights Reserved.DOMOREA C E 2 0 1 3
  2. 2. aras.comCopyright © 2013 Aras. All Rights Reserved.A C E 2 0 1 3Strategies for ImplementingAras InnovatorLearn how to effectively plan andimplement Aras Innovator using bestpractices and methods proven by Arasto make your deployment a success.
  3. 3. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 3Agenda Our Approach Aras Methodology Getting Started Getting it Done What to watch for Final thoughts
  4. 4. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 4Our 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
  5. 5. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 5Guiding Principles Individuals and interactions over processes and tools Working software over comprehensive documentation Collaboration over contract negotiation Responding to change over following a planAgile Manifesto2001
  6. 6. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 6Iterative ApproachInception Elaboration Construction TransitionEnvision&PlanIncrementally define and build aconsumable solutionRelease&Rollout
  7. 7. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 7Why Iterative Development It favors working solutions over detaileddocumentation that has little value to end users It provides the mechanism to continually refinerequirements It is proven to deliver a solutions that meet theneeds of real end users. Traditional systems, like Waterfall, tend to fixrequirements at the start of a project This very rarely produces the desired result
  8. 8. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 8Compare ApproachesValueDrivenRequirements(Scope)DateResources(Cost)PlanDrivenRequirements(Scope)Resources(Cost)DateEstimatedFixedTraditionalApproachesIterativeApproaches
  9. 9. BREAKING DOWN YOUR PROJECTMANAGEABLE PHASES
  10. 10. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 10The Big PictureDisciplinesBusiness ModelingRequirementsAnalysis & DesignImplementationTestDeploymentConfigurationManagementProjectManagementPhasesInception Elaboration Construction TransitionI1 E1 E2 C1 C2 C3 T1 T2Milestones
  11. 11. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 11Inception 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 senseSlide 11
  12. 12. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 12Elaboration 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 placeSlide 12
  13. 13. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 13Construction 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 plannedSlide 13
  14. 14. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 14Transition PhaseDeploy 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 productionSlide 14
  15. 15. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 15An Innovator ProjectSlide 15Disciplines ActivitiesInceptionInitial Parts Change Parts Change Interface T1 T2Install Test EnvironmentTrain Project TeamKickoff MeetingHigh Level RequirementsDiscovery workshop(s)SoWProject Charter & Solution OverviewHigh Level Use CasesRequirements WorkshopsRequirements Document(s)Gap analysisUse Case DevelopmentSolution Design DocFunctional specs for customizationsScreen MockupsVisual PrototypesImport UsersConfigure ItemsConfigure FormsConfigure WorkflowsConfigure Roles & PermissionsBehavioral PrototypesDevelop Data MigrationInterface developmentDevelop CustomizationsPrepare Test PlanUnit TestFull System TestPrepare User DocsDevelop User TrainingDeliver User TrainingBuild & Deploy Prod EnvProduction Data MigrationPackagingMigrate Dev-QA-ProdChange ManagementInitial Project PlanInitial Risk AnalysisProject Planning & Design ReviewMilestonesTIMEPhasesElaboration Construction TransitionProject StartupBusiness ModelingRequirementsProject ManagementAnalysis & DesignImplementationTestDeploymentConfiguration Management
  16. 16. GETTING STARTED
  17. 17. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 17Getting 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 analysisSlide 17
  18. 18. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 18How to approach itDivide and Conquer Divide implementation into phases Preferably phases that provide business values and can bedeployed independently Build a plan for each phase Choose goals for each phase and make sure you addressitems 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 iterativelySlide 18
  19. 19. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 19ResourcesWho do you needRole ResponsibilityProject Manager • Direct Implementation resources• Manage project schedules• Track Status• Resolve conflicts and issuesBusiness Process Owner(s) • Provide project priorities and objectives• Direct participation of resources• Resolve business process issuesSubject Matter Experts • Communicate current process• Provide information details• Support user community during rolloutI.T. System Support • Support site infrastructure• Extract legacy data• Provide technical expertiseTechnical Resources • Configure application• Develop customizations• Provide technical expertiseSlide 19
  20. 20. GETTING IT DONE
  21. 21. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 21Getting It DoneElaboration - The key points Make sure you achieve concurrence on requirements This provides mutual understanding and prevents individualinterpretations 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 riskSlide 21
  22. 22. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 22Getting 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 feedbackSlide 22
  23. 23. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 23Regular ReleasesDevelopment Release for User validationProduction Release
  24. 24. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 24Getting 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 materialsor train end users Production Cutover Plan, Plan, Plan, - there will be external influencesSlide 24
  25. 25. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 25Making Iterations WorkThings to think about Work is done in a serial fashion but you don’t needto 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 plannedSlide 25
  26. 26. BEST PRACTICES
  27. 27. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 27Implementation 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 anddesign 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
  28. 28. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 28How Things Get Sideways Lack of requirements understanding or agreementon requirements Lack of understanding of the standard ArasInnovator solutions Lack of Training Underestimating the impact of change Biting off too much!Slide 28
  29. 29. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 29Final ThoughtsDos and Don’ts DO Get Trained Create visual prototypes and get user validation beforedeveloping 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/oprototyping the solution Worry about not getting 100% of the detailedrequirements up front - because you won’t!Slide 29

×