The Process of Using Formal Analysis and Interpretation to Evaluate a Work of Art
Most of us in the Data Engineering earth are busy people. We are certainly in the historic period of push engineering overload and minimizing wasteful piece of work at personal, professional person and corporate level is a constant goal.
From the Agile Manifesto, at that place are twelve principles[ane] related to software delivery. All the principles still have deep meaning 15 years after the establishment of them, only 1 that repeatedly resonates with me is the tenth principle: "Simplicity–the 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 time, they will often question the thought of "maximizing the amount of work not done". Why would one maximize not doing something? Well, the concept shouldn't be that tricky to understand. Let me provide a common example.
For me, context switching is a daily challenge to manage. In my task, there are abiding interruptions in the form of calls, Instant Messages, texts, emails and the old fashioned tapping on my shoulder. I've had an old, rather bad habit of wanting to "proceed my inbox" clean and checking my e-mail throughout the day. Apparently I'm non the only one since over a third of Americans follow me in this practice[2]. This is a productivity killer since I'm e'er switching between focused piece of work and my emails. This doesn't follow the Kanban-inspired "Stop Starting, Start Finishing" mantra.
So more oft now, I proceed my email closed throughout the twenty-four hour period and merely go into it similar to spelunking into a cave. Bank check it out but a few times a twenty-four hours. Productivity appears to have risen since I find myself finishing more than before going on to the next task. So this is about maximize the amount of work non washed. Don't check on e-mail regularly since information technology's a productivity killer.
Now let's accept this Lean-Agile principle to the software evolution world. From Donald Yard. Reinertsen's volume, "Flow"[three], there is a balance between the frequency of whatsoever transition (i.due east. checking your email) and the holding cost (i.east. others waiting for you to answer your email). This balance is very catchy to meet since it is dependent on the situation. If you get urgent emails daily that crave instant attention (product system alerts, major back up incident, etc.) so checking your email frequency would be necessary.
See the below overall conceptual chart of how to maximize your flow. Sometimes, maximizing menstruation is clear and easy when at an individual level. However, at the organizational and squad levels it becomes far more complicated. Simply through tracking and measuring the results will you lot be able to determine the optimum place of maximizing the work not done. Note sometimes the results will exist surprising!
And then accept for instance Scrum ceremonies like backlog refinement, sprint planning, dart reviews, sprint retrospectives and of course, the daily stand up. If we consider the daily standup, many team members often observe it a "waste of time". That may indeed be the case. For instance, if the team is collocated and regularly talk together, they may already have this key points of a stand up known to each other. Using tools like Jira, TFS, CA Technologies (once Rally), VersionOne, etc. volition also decrease the "chatter". In this instance, reducing the number of standups may actually be the best remedy and increase the amount of work non done.
Scrum has a gear up of tools with a recommended set up of cadences that should exist synchronized in gild to simplify delivery and therefore maximize the piece of work non done. This recommendation should be adjusted based on the needs of the system. Scrum is flexible, but still organized simply at a different levels.
A diligent leader will always be seeking for these areas of waste material and pointing those out to their staff to address their ain organizational bottlenecks, reducing the corporeality of waste material. For instance, I've seen the Outlook calendar for a specific CTO in a large retail company where his schedule was booked pretty much 100% from usually 7am – 5pm every single 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 work not done by blocking out time for completing priority work and thereby freeing upwardly the resulting traffic jam for unexpected events.
So when you are in the eye of your busy work solar day, remember to continuously seek ways to maximize that work not done. This is a never ending process and will always demand action or otherwise decrease your enterprises' ability to perform.
[one] http://agilemanifesto.org/principles.html
[2] http://www.businessinsider.com/how-often-do-people-bank check-their-email-2015-eight
[3] http://ardalis.com/principles-of-product-development-flow-volume-review
Source: https://www.cio.com/article/238531/the-art-of-maximizing-work-not-done.html
0 Response to "The Process of Using Formal Analysis and Interpretation to Evaluate a Work of Art"
Postar um comentário