Go/No-Go Proposal--Draft

stan_koprowski

Agenda:

1. Review goals
2. Restate business problem
3. Review Alternatives / Options considered
4. Recommended Solution: Why? Approach, Project Plan

Alternatives considered:

1. Do nothing business as usual
2. Hire sales assistants to augment international staff to eliminate double data entry
3. Integrate with existing systems as necessary
4. Sales use Orion for opportunities / SFDC for lead management, forecasting, campaign management
5. Evaluate new SFDC modules ( 100 users / year: $100,000 )
   • 10% growth of HC / year
   • 5% price increase / year
   • Maintenance
   • Support
   • Training

Recommendations

      Go: Integrate with existing systems as necessary

       No-Go:

--To be determined...--

Please note even with a no-go decision some additional considerations still need to happen

 

Benefits of proposed solution

 --To Be Added--

Assumption of solution:

Training for sales, management, business operations, SE,  PRIOR  to production use

Solution Approach:

1. Iterative approach
   • Model, data dictionary, process steps
   • Design, develop, build
   • Testing
   • Bug Fixing
2. Production
   • Department level training
   • Production regression testing
   • Maintenance activities

 Project Planning (Work Packages) 

 

Snapshot Salesforce2COMIT Draft Project Plan Project management activities

1. Iterate through each BUC
   • Building
     1. SFDC database changes
     2. API development
2. Requirements gathering
   • Context diagram
   • Defining data dictionary
   • Defining process flow
   • Define Activity steps for each process
   • Non-functional
3. Contract dashboard / reporting
4. Business proposal approval workflow
5. Testing
   • Define test cases
   • Write test cases
   • Regional specific product offering
   • Execute test cases
   • Review results
6. Bug Fixing
   • Create updated models
   • Update data dictionary
   • Update code base
7. Training (wait until all modules are complete, rolled up into completed state)
   1. Rationale / Why?
      • Difficult to maintain two separate processes
      • Additional changes required resulting from integration testing
      • Iterative rollout approach can be more disruptive to sales cycles
   2. Management training
      • Understanding role in process
      • Execution
   3. Sales training
      • Prepare training documents
      • Review training documents
      • Conduct training
        1. Systems
           1. GIDB
           2. ATLAS
           3. SFDC
        2. Sales Staff
           1. Field sales (existing staff)
           2. New hire onboarding training
           3. Inside sales (existing staff)
           4. New hire onboarding training
           5. Regional based?
        3. Business Operations training
           1. Prepare training documents
           2. Review training documents
           3. Conduct training
        4. SE training
           • Existing
           • Onboarding
        5. Timing
           • Prior to production
           • refresher
8. Timing for updates / changes
   • Fee schedules if relying on JMP calculations by Sept 30, otherwise ok
   • New year territory changes by December 1
   • New product offering
   • Regression tests
   • New Employees
   • Dependent Systems