Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Practice Exercises and Glossary

Practise ERP and CRM implementation, data, integration and selection skills with graded exercises and runnable self-checks, plus a glossary of the key terms from this track.

You have now covered the implementation, data, analytics and selection side of ERP and CRM. This final lesson gives you exercises to test and extend your skills, with runnable checkers in Python, and a glossary of the terms that appear most often in projects and vendor conversations.

Work through the exercises in order; each one has a small starter and a check. The products themselves are not available on this site, so every exercise is a stand-in model.

How to practise

  1. Try the exercise first without looking at hints.
  2. Edit the code in the editor and press Run.
  3. Compare with the check output; if a check fails, read its message and fix the cause.
  4. Write one sentence explaining the business meaning of your answer. That sentence is the real skill.

Exercise 1: Fix the plan (implementation)

The schedule below has a dependency mistake: UAT is scheduled to start before integration testing finishes. Fix the start weeks so every task starts after all its dependencies, then compute the project length.

Python Exercise 1: dependency checker

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise 2: Classify the gaps (fit-gap)

For each requirement choose one of: fit, configuration, extension, custom, process change. The checker marks answers against a reasonable model solution and explains. Disagree? Write down why: there is often more than one defensible answer when you can justify it.

Python Exercise 2: classification

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise 3: Cleanse the extract (data)

Complete the clean() function (it currently returns the rows unchanged): trim spaces, uppercase the country code, map UK to GB, lowercase emails, and drop rows with no name. The test below counts your result.

Python Exercise 3: cleanse and test

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise 4: Make the integration safe (integration)

The receiver below creates a duplicate order when the same message arrives twice. Add idempotency so the second delivery is ignored (the seen_keys set is there for you). The test sends each message twice.

Python Exercise 4: idempotent receiver

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise 5: Rank the vendors (selection)

Using the weights below, compute the weighted score per vendor and decide. Then raise the weight of "price" to 40 (and lower "fit" to 20) and see if the winner changes.

Python Exercise 5: weighted decision

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise 6: Compute the business case (TCO and ROI)

The code finds the first year in which the cumulative cash flow is positive. Run it, then reduce the year-3 and year-4 benefits by 100,000 each and predict, before running, whether the payback year changes.

Python Exercise 6: payback year

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Discussion questions

Use these in a team or study group; there is no single right answer.

  1. Your sponsor wants a big bang go-live in December, but testing finished late. What do you present to the steering committee?
  2. A department asks for 15 customizations. How do you decide which to keep?
  3. Sales reps do not record activities in the new CRM. List five possible causes and what you would measure.
  4. A vendor's SaaS release changed a screen your users rely on. What process would have protected you?
  5. Two systems show different customer addresses. Who decides which is right and how is it fixed for good?

Glossary

Term Meaning
API A defined interface that lets one program call another, usually over HTTP with JSON
Big bang Switching all modules and sites to the new system on one date
Blueprint The signed-off design of future processes and the system
Change control A formal process to approve or reject changes to scope, design or schedule
Churn Customers who stop buying or cancel
Critical path The longest chain of dependent tasks; it sets the project length
Cutover The controlled switch from the old system to the new one
Data owner / steward The accountable business person for a data domain / the person who maintains its quality
Dead-letter queue Holding area for messages that could not be processed
Fit-gap analysis Comparing requirements with standard product capabilities
Golden record The best merged version of an entity built from several sources
Hypercare Intensive support after go-live
Idempotency Handling the same message twice has the same effect as once
iPaaS Integration platform as a service: a cloud hub for connecting systems
KPI A metric tied to a goal with a target and an owner
Master data Shared, slow-changing business objects such as customers and products
Multi-tenant Many customers share one platform and code base
NPV / IRR Net present value / the discount rate at which NPV is zero
OTIF On time, in full: share of orders delivered correctly
Pilot An early go-live of a small unit to prove the design
RFI / RFP Request for information / for proposal in vendor selection
RFM Recency, frequency, monetary value: a customer segmentation method
Rollback Returning to the old system if cutover fails
SaaS Software as a service: rented, vendor-run software
SLA Service level agreement: promised availability and support response
Super user A trained department member who coaches colleagues
TCO Total cost of ownership over the system's life
UAT User acceptance testing by business users
Webhook A call a system makes to your URL when something changes

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In Exercise 1, what makes a schedule inconsistent?

    Dependencies require predecessors to finish before the dependent task begins.
  2. 2. Which term describes processing the same message twice with the same effect as once?

    Idempotent receivers can accept retries and duplicate deliveries safely.
  3. 3. A weighted scorecard winner flips after a small change in weights. What should you conclude?

    A ranking that depends on tiny weight changes cannot be trusted without further analysis.
  4. 4. Which of these is NOT an ERP or CRM implementation phase from this track?

    Compiler optimization is a programming topic; the others are normal project activities.

Summary

  • Practise with small models: schedules, classification, cleansing, idempotency, scoring and business cases.
  • Always attach a business meaning to the numbers you compute.
  • The glossary collects the vocabulary of implementation, data, integration, analytics and selection.
  • Return to the track page to revisit earlier chapters and keep building real-world experience.

Next: Back to the ERP and CRM Fundamentals track