In this session, we want to share with you lessons learned from Legacy CFML projects that we have lead and implemented so you can learn from both our mistakes and our success.

1. Press Start
LESSONS LEARNED
from 250+ Legacy Apps

2. Player 1 Player 2
Jorge Reyes Esme Acevedo

3. What is a project?
A temporary endeavor undertaken to create a
unique product or service

4. Doing Legacy
Migrations
since 2015

5. What Worked
Repeat Fine Tune
Play Again
HIGH SCORE
8800

6. GAME OVER
What Didn’t Work
Try Again
Failing is a Learning Opportunity

7. –Thomas Edison
“I have not failed. I've just found 10,000 ways
that won't work.”

8. INDICATORS OF A SUCCESSFUL
PROJECT
•Budget
•Timeline
•Customer Satisfaction

9. •Scope
•Cost
•Time
•Quality
•Resources
Competing
Constraints

10. •Scope
•Cost
•Time
•Quality
•Resources
Competing
Constraints

11. •Scope
•Cost
•Time
•Quality
•Resources
Competing
Constraints

12. •Scope
•Cost
•Time
•Quality
•Resources
Competing
Constraints

13. •Scope
•Cost
•Time
•Quality
•Resources
Competing
Constraints

14. Before you Start

15. In-depth
Discovery
Analysis
& Planning

16. AVOID!

17. NO SOW, NO SHOW

18. Estimates
are not just
a Number

19. Formally
evaluate
new
technologies
BOSE WEARABLE SPEAKER

20. Think BIG
Start small

21. Define a
Product
Owner
(Singular)

22. Ensure the
right
mindset and
clarify
expectations

23. Get to
know the
legacy
team

24. List your “Smart Friends”

25. Consider the
transition phase
from the get-go

26. Have an
on-site
planning /
kick-off
session

27. Lessons During Development

28. IT’S DANGEROUS TO GO ALONE! TAKE THIS.
SOLO Legacy Projects are absolutely forbidden
FRONT-END
DEVELOPER
BACK-END
DEVELOPER

29. Resources
•Define the processes for
sharing, updating,
changing and maintaining
assets.
•Document your legacy
migration process.
•Establish code guidelines.

30. GOLD PLATING
•You'll have to fine tune it
•It may even start giving you trouble!
•Do not allow scope creep to creep out.

31. IMPLEMENTATION BREAKDOWN

32. PM POINT OF CONTACT

33. TICKET SYSTEM
•Ensures visibility
•Allows for effective
communication
Jira, Gitlab, PivotalTracker, zendesk

34. Player 1 Branch
Player 2 Branch
16 hours ago
2 hours ago
Branch Updated
Source-Control
Convention and Plan

35. After
Final Delivery

36. Capture
Lessons Learned

37. THE END
LESSONS LEARNED
from 250+ Legacy Apps