📚 Introduction
Every project, big or small, is a new journey and will give rise to new experiences. Make your journey as smooth as possible by gaining from these historical lessons learned and contribute to this body of knowledge when you have a lesson yourself to share with others!
🎒 Lessons learned
Category | Added by | Date | Lesson learned | Best practice or issue? | Advice | Follow up |
|---|---|---|---|---|---|---|
Getting started | Frank | 27-5-2024 | Setup new concern continuous disrupting. Not only configurations, but also backend settings like authentication tokens and MXTS user log-out time | ISSUE | Improve generic process. Setup & test configurations before introducing client to it. | Discussed internally |
Getting started | Frank | 27-5-2024 | Put testable configuration in place on ACC to introduce new users, rather than starting up from zero. | BEST PRACTICE | Setup testable configuration based on Maxxton advice, so new users can experience the system and validate / confirm suggested configuration. | Add in implementation guide |
Data migration | Frank | 27-5-2024 | Always have scripted data imports validated via script as well on test environments, before importing on Live. (Does imported data matches source data). | ISSUE | Avoid surprises and complex corrections, of which time spend easily exceed effort to create validation scripts. | Add in implementation guide |
Project approach | Frank | 27-5-2024 | Agile mindset enables successful projects; hit deadlines, reduce scope if needed, customer doesn't need everything | BEST PRACTICE | Explore to what extent an agile approach can be used for a project (Agilometer) | Add in implementation guide |
Project approach | Frank | 27-5-2024 | Consider using new features (meaning not elsewhere in live use) by default as 'increased risk'. Only consider these features 'done' when used in Production (in bulk if applicable). | ISSUE | Put new features in Live use as soon as possible. Either via testing on Production or putting a small scope in live use early (pilot). | Add in implementation guide |
System | Frank | 27-5-2024 | Bugs reduce confidence. This leads to quite some (ineffective) time spend to test, reproduce, report, discuss, monitor bugfix, and regaining confidence. | ISSUE | When targeting shorter durations of implementations, a bugfree system is essential. Or if bugs are present these should prioritized for fixing rather then postponing. | Discuss internally |
Configuration | Frank | 27-5-2024 | It is essential to have documentation of implications for configuring resources at parent level or location level, as well as the implications of multiple levels in location hierarcy. | ISSUE | Create documentation with benefits, limitations and implications of configuration options. This improves velocity in decisionmaking for configuration setup. | Create infographic |
Project approach | Frank | 27-5-2024 | High priority and update-rythm for critical path 'products' where uncertainty is. | ISSUE | For any project critical products where uncertainty is present, an ongoing weekly focus should be present to avoid worries and late / overdue delivery. | Add in implementation guide |
Project approach | Frank | 27-5-2024 | Availability of use cases for user training. | ISSUE | There should be a default list of use cases which can be used to quickly create a scope for testing / user training. | Add in implementation guide |
Â