Basic mindset for being agile

<a developer perspective />

When you take a look at the Agile ‘Software Development’ Manifesto it is all about solving issues faster in a cooperative style. They claim: “We are uncovering better ways of developing software by doing it and helping others do it.”. The word ‘software’ can replaced by a solution for a job, a neccessary coding task for business. Or, even more abstract, as any value focusing on outcome. The target changes but not the necessary mindset.


Transparency

Delighting urgent blockers or unresolved side-dependencies while doing your job is a clear statement. It is important to point out the problem to the right person at right time.

Stack at work

Frequently disturbing others or get an answers in hurry will not help you for your quality of results. Do not take this as a general shortcut. First, prepare yourself. Take around 5 minutes and summarize your thoughts. Demonstrate where you stack and share your possible ways how to solve it. You negotiate together next steps, you get tips and hints to prevent conflicts or cut work packages.

Daily reporting

Use a time-boxed 15 minutes meeting routine at your team half an hour before lunch time. Call it Daily (Scrum). You, like everybody else, have 1 minute to say what is your focus for rest of working day and what you need from whom. Right after the meeting you can share the details in a one-on-one, schedule a 10 to 20 minutes meeting with (minimum) needed participants or go for lunch together.

Planning routine

Near the end of working time you plan your tomorrow’s day. Invest 10 minutes to sum up your tasks for yourself. Ask the questions ‘What is the status’ and ‘How much time I’ll need until I’m done’. Update your tasks scheduler / ticket system or write it down on a sheet of paper. Mark most important and most urgent task which you will do first. Recap next morning and start working.


Do not hide yourself behind your monitor.

To summarize, do not fear about being transparent. Challenge yourself and create confidence while talking louder about your good news to team and your limitations while working. Be active player to discover blockers and be responsible about your tasks.

You will realize positive productivity effects. You keep your work flowing. You are more collaborative and done tasks faster. (Try to) Apply the three given actions and share your experiences. I would like to read your comments: especially from other roles which are involed in agile processes.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.