A week-by-week plan across Units 1 to 6 plus the capstone, with practice systems, certifications worth considering, a GitHub portfolio, community writing and mentors.
Watch firstThe first 20 hours -- how to learn anything | Josh Kaufman | TEDxCSU · TEDx TalksOpen on YouTube ↗
Principles for the next 90 days
Thirteen weeks at eight to ten hours a week is roughly 110 to 130 hours. Three rules: build, don't just watch (every week ends with something that runs or is written); ship in public (push to GitHub weekly); review on fixed dates (day 30, 60, 90). SAP technical units come first because they are hardest to learn alone.
A suggested split of about 120 hours over 13 weeks.
The plan at a glance
Start the capstone's synthetic data and profiling in weeks 8 and 9, alongside Unit 4; it takes pressure off the final fortnight.
Day 30 checkpoint after week 4, day 60 after week 9, day 90 after week 13.
Week by week
The proof column is what you will link from your CV.
One repo per phase, all linked from a profile README.
Try it · Sort
Which 30-day block does each activity belong to?
Days 1-30 (wk 1-4)
Days 31-60 (wk 5-9)
Days 61-90 (wk 10-13)
Click an item, then a bucket (or drag it).
Practice systems
Check current terms on SAP's sites before signing up. MDG itself is rarely free, so design the MDG parts and practise ABAP and CDS in the trial. Set a monthly spending limit on any LLM API key, and keep the key in an environment variable or a .env file listed in .gitignore, never in a repository.
Free options cover ABAP Cloud, CDS, RAP and Python; real MDG usually needs an employer sandbox.
Try it · Match
Match each option to what it is good for.
Pick an item on the left, then its match on the right.
Certifications worth considering
A certificate does not replace a demo, but helps pass CV filters. Order for you: MDG first (confirms depth), then ABAP Cloud (biggest gap); CAP and Generative AI only if you target BTP side-by-side roles. Names and codes change; verify on learning.sap.com before booking.
Names and codes as published at time of writing. Always check learning.sap.com.
Portfolio and writing
GitHub is your technical CV: a profile README with your three-line pitch, pinned repos in reading order, ABAP stored with abapGit. After each phase, write one short SAP Community or LinkedIn post: what you built, one diagram, one surprise. Two or three in 90 days is enough.
Pin the capstone first; everything else supports it.
The weekly rhythm
Step through · 1 of 5
Sunday evening, 15 minutes: pick the lessons and the one thing you will build. Write it as one sentence at the top of your notes.
Plan, learn, build, write, review: about 8 to 10 hours a week.
Mentors and community
Find three or four people for occasional specific questions: a senior technical MDG consultant, an ABAP Cloud developer, someone in SAP AI or data. Use the network you have: Deloitte colleagues, former Cognizant teammates, PGDM classmates. Answer MDG questions on SAP Community. By day 90: capstone pinned with video, two or three posts, a certification booked or passed, updated CV and LinkedIn.
Try it · What would you do?
You want feedback from a senior technical MDG consultant you have never met. Which message do you send?
Remember
Plan about 120 hours over 13 weeks: SAP technical units first, then Python and AI, then the capstone.
Certifications: MDG first, ABAP Cloud second; verify names and codes on learning.sap.com.
Publish weekly on GitHub, write two or three posts, and ask a few people specific questions.
Check yourself
Which certification order fits a functional MDG consultant moving to technical MDG?
Where can you practise ABAP Cloud, CDS and RAP without an employer system?
You fall behind in week 7. What does the plan recommend?