Examplestwo Dimensional Art Work and Principle of Asymmetrical Balance in the Louvre

Nearly of us in the Information Applied science world are decorated people.  We are certainly in the age of button technology overload and minimizing wasteful work at personal, professional and corporate level is a constant goal.

From the Agile Manifesto, at that place are twelve principles[ane] related to software commitment.  All the principles withal take deep meaning 15 years later the establishment of them, only 1 that repeatedly resonates with me is the 10th principle: "Simplicity–the fine art of maximizing the amount of work not done–is essential".

When I've asked people who have been in the Information technology industry for a long fourth dimension, they volition often question the idea of "maximizing the amount of work non done".  Why would one maximize not doing something?  Well, the concept shouldn't be that tricky to understand.  Let me provide a mutual example.

For me, context switching is a daily challenge to manage.  In my task, at that place are constant interruptions in the grade of calls, Instant Messages, texts, emails and the one-time fashioned borer on my shoulder.  I've had an sometime, rather bad habit of wanting to "go on my inbox" make clean and checking my email throughout the day.  Plainly I'm not the only one since over a tertiary of Americans follow me in this do[ii].  This is a productivity killer since I'm ever switching between focused work and my emails.  This doesn't follow the Kanban-inspired "Stop Starting, Beginning Finishing" mantra.

And so more frequently now, I keep my e-mail closed throughout the mean solar day and only go into it like to spelunking into a cave.  Bank check it out only a few times a day.  Productivity appears to accept risen since I find myself finishing more before going on to the next job.  So this is about maximize the amount of work not washed.  Don't cheque on email regularly since information technology's a productivity killer.

Now let'south take this Lean-Agile principle to the software evolution world.  From Donald G. Reinertsen'due south book, "Flow"[3], there is a remainder between the frequency of any transition (i.e. checking your email) and the belongings cost (i.east. others waiting for you to respond your e-mail).  This balance is very tricky to meet since it is dependent on the situation.  If you get urgent emails daily that require instant attention (production system alerts, major support incident, etc.) and then checking your email frequency would be necessary.

Run into the below overall conceptual chart of how to maximize your flow.  Sometimes, maximizing flow is articulate and easy when at an private level.  Notwithstanding, at the organizational and team levels it becomes far more complicated.  Only through tracking and measuring the results volition you lot exist able to decide the optimum place of maximizing the work not done.  Note sometimes the results will be surprising!

And so take for case Scrum ceremonies like backlog refinement, sprint planning, sprint reviews, sprint retrospectives and of course, the daily stand up.  If we consider the daily standup, many squad members often notice information technology a "waste of time".  That may indeed be the case.  For instance, if the squad is collocated and regularly talk together, they may already have this key points of a stand up up known to each other.  Using tools like Jira, TFS, CA Technologies (once Rally), VersionOne, etc. will too decrease the "churr".  In this case, reducing the number of standups may actually be the best remedy and increase the amount of work non done.

Scrum has a set up of tools with a recommended set of cadences that should be synchronized in order to simplify delivery and therefore maximize the work non done.  This recommendation should be adapted based on the needs of the organization.  Scrum is flexible, merely still organized but at a dissimilar levels.

A diligent leader will always exist seeking for these areas of waste and pointing those out to their staff to accost their own organizational bottlenecks, reducing the amount of waste.  For instance, I've seen the Outlook agenda for a specific CTO in a large retail company where his schedule was booked pretty much 100% from usually 7am – 5pm every unmarried mean solar day.  Akin to a freeway at 100% usage, this brings his productivity down to a minimum where working early mornings and evenings becomes necessary for daily work and less on longer term vision, innovation and growth.  He should focus on maximizing that piece of work non washed past blocking out time for completing priority work and thereby freeing upward the resulting traffic jam for unexpected events.

 Then when y'all are in the middle of your busy work twenty-four hour period, recall to continuously seek ways to maximize that work non done.  This is a never catastrophe process and will e'er demand activity or otherwise decrease your enterprises' ability to perform.

[one] http://agilemanifesto.org/principles.html

[two] http://world wide web.businessinsider.com/how-oftentimes-do-people-check-their-email-2015-8

[iii] http://ardalis.com/principles-of-product-development-catamenia-volume-review

kellumlester.blogspot.com

Source: https://www.cio.com/article/238531/the-art-of-maximizing-work-not-done.html

Share this post