Probably, you heard about Day 0/ Day 1/ Day 2 somewhere in your journey with IT. In fact, you probably heard about them in different areas as well. I am trying now to explain it and how it is used in different contexts.
Generally speaking, Day0/1/2 is used in the software lifecycle. It refers to the software lifecycle phases, from the design phase to the go-to-life phase, and continues.
Day 0
It is the very first day of everything, when we set together and start brainstorming a new software, this phase is all about “HOW WE START”
In this phase we can see:
- Architecture, Design, and Strategy
- Studying and focusing on customer needs,
- service goals and values “how to keep the service runnings”
- Business – budget, cash flow, ROI, vendors management (and other kinds of stuff)
Of course, it is expected in this phase lots of meetings and writing documents and reports. In fact, this is boring but it is a MUST because it is like the ground phase that we cannot build on without. That’s why design skills are kind of important in any type of enterprise. Or simply, let an enterprise start a project “any project” without planning and design, and see how they drift away.
Day 1
You did a design phase on Day 0? so, let’s apply it in the development and deploy what you did.
This phase is about everything in “DEPLOYMENT”, so, it is not only about building and developing the application itself, but also everything related like infrastructure, networking, and any external service. and make sure that everything is connected and worked together.
The most wonderful thing about this phase is that it is the phase of creativity. When you see writing on the paper and some graphs transformed into a real thing….. Interesting.
Day 2
Going live with your project is a remarkable moment. When your product is available to use by your customers.
In this phase, the focus will be on monitoring, optimizing, and maintaining the services. Watching out for anomalies or unexpected behaviors.
This is how we work, to maintain, observe, analyze the feedback, then decide and act accordingly. This is what we call “Normal Operation”. That’s why there is a “Day N”, which means that it is a continuous job.
This model was handled separately in each phase. But today’s work, we have the AGILE METHODOLOGY that makes it like “day-to-day” work. In fact, day 0 and day 1 are working together even if day 2 is near.
From this perspective, you can apply Day 0/1/2 to your operation in any industry. Even in the military, they used to use those terms in their daily operations.
Former Nuclear Engineer | University Lecturer | Technology Advisor | Digital Transformation evangelist | FinTech | Blockchain | Podcaster | vExpert ⭐️⭐️⭐️⭐️ | VeeamVanguard ⭐️⭐️ | Nutanix SME | MBA | AWS ABW Grant’23
