Fostering Agile outside of the World of Software

New to this side of the world- what is equivalent to the ABCs for software developers, has my mind completely blown.

In times where I’ve struggled with making the “perfect” end product, overwhelming stress and getting the task done- Agile methodology and the principles of Scrum could have been the magic solution. Not as the outcome itself but rather the framework that would help me create it.

Though best implemented in software innovation conditions, I find that aspects from every step of the process would benefit us all regardless.

Here are some things I will personally be adopting into my work ethic:

Defining Done:

A crucial first step in the process is forming a clear definition of done. It acts as the end goal for each sprint and progress is measured as a percentage of the DoD achieved. In situations of ambiguity, I can create a metric to adhere to and help curb the negative after effects of my (sometimes) “it’s good but not perfect” mindset to work outcomes.

Change Roles not Structures:

Now I don’t know about you, but I have struggled with meticoulous planning and the frustration that comes with things naturally not going to plan. If I plan in detail only the activities that wont change before execution- I can accomodate for more flexibility. By building a "roomy" framework, I have space to change roles and adapt for new requirements without the structure crumbling and stress overflowing. This will be especially helpful when working with teams at university and at work.

The MVP:

While I run after creating the right impression and getting things right, I can get stuck in a loop of procrastination and ineficiency. Instead, I can go with the "answser first" approach and form what scrum teams like to call the "Minimum Viable Product." With a clear first base where the MVP is formed- increments of improvement will be easier and faster to add on, thus saving me time and encouraging productivity.

Sprint retrospective:

While the review is just as important, I find that a frequent sprint retrospective is something I must incorporate into my work ethic. At the end of each task- looking back at how things were done, what worked, what was lacking, and what needs to be done more is imperative in adapting processes for better efficiency. Doing this on a task by task basis may help me much more than leaving it only for when things go awry.