WHAT IS THE TIP?
💡 Managing your "Push to Live" process should be both smooth and efficient. Changes are made in the Config environment, thoroughly tested, and then pushed to Live. To keep everyone in the loop, we add locks on the system for each change being made.
Since we handle the system as a whole rather than in individual parts, it’s super important to make sure those locks are added and signed off before the push. The Oleeo QC team then takes care of the push itself, ensuring everything goes smoothly. Here are some handy tips to help you manage this process like a pro!
Â
Schedule Your Pushes – Save Time and Stay in Control
💡 Why not schedule your pushes ahead of time? Instead of raising a Sugar case every time you need a push - which requires the QC team to pick it up and action, potentially causing a slight delay - you can actually schedule your pushes yourself. This way, you can choose the exact time that suits you best, cutting down on wait times and keeping everything under your control.Â
Â
Simply include your preferred time and date in the Sugar case for your self-config push request, and we’ll handle the rest. Please ensure you provide at least 24 hours' notice for scheduled pushes.
Â
Use Case: Let’s say you’ve got a bunch of updates that need to go live first thing in the morning. By scheduling the push, you can set it up to happen exactly when you want, without any hassle.
Â
Sprint Systems – Perfect for Busy Periods
💡 Manage multiple changes easily with a sprint system. When you’ve got a lot of changes to make, a sprint system could be your best friend. Some of our customers set up three-week sprints to help organise their work; this process will allow them to comfortably handle changes, test them, and fix any issues before the final push to Live. This approach helps you prioritise your work, keeps things on track, and makes sure everyone knows what to expect.
Â
Use Case: If you’re juggling several updates across different parts of the system, a sprint cycle helps you stay organised, ensuring everything’s tested and ready to go for a seamless push to Live.
Â
Avoid Friday Pushes – Be Prepared for Any Issues
💡 Don’t schedule pushes on a Friday! Why? Because if something unexpected happens, it might be harder to get the immediate support you need over the weekend, or even be notified of an issue by your candidates. By scheduling pushes earlier in the week, you ensure that our team is fully available to help resolve any problems that might arise.
Â
Use Case: If you’re planning a major update, scheduling it for a Tuesday or Wednesday gives you the rest of the week to address any problems, ensuring a smoother process.
Â
Maximise Your Self Config Push Request - Top Tip When Raising Your Cases
💡 Save time - Just copy and paste all your lock names into one case instead of raising multiple cases for all your changes!
Â
Use Case: If you regularly make multiple changes, raising one case rather than several at a time will really reduce your admin time and burden.
Â
😊 Share Your Best Practices! We’d love to hear how you manage your "Push to Live" process in Oleeo. Do you have any tips that help ensure smooth updates and minimise disruptions?Â
Â
BENEFITS
- Save Time: Scheduling pushes and avoiding Fridays means less waiting around and more peace of mind.
- Stay Organised: A sprint system and clear communication help you manage multiple changes smoothly and keep your team aligned.
Â
CONSIDERATIONSÂ
-
Coordination with Other Teams: Ensure that all relevant teams are aware of the scheduled push. If different teams are working on interconnected systems or features, it's crucial to coordinate to avoid conflicts and ensure a smooth transition.
-
Testing Thoroughness: Before scheduling a push, double-check that all necessary testing has been completed and that any potential issues have been addressed. Pushing untested or partially tested changes can lead to unexpected problems.
Â
COSTS
This feature is part of the standard product offering.
