sometimes work doesnât look like work (+ 5 more agile principles that apply to everything)
I came across this article via Twitter at precisely the right moment.Â
The kiddos (now in 5th and 8th grades) just returned to school this week.Â
It hasnât been pretty.Â
Already, the 5th grader has forgotten a school book for homework. And the next day, he forgot to do part of his homework (even after being asked, âDid you do all your homework?â And answering yes. Heâs 11. Iâm not checking his folder anymore. If he doesnât do it, he faces the consequences ... ).Â
I think things are going better with the 8th grader, but ... sheâs gotten scary-good at knowing exactly what to say to appease me. Regardless, sheâs already complaining about the workload this year requires.Â
So even though we had a family meeting the night before school began (during which we discussed organizing, planning, using kanban), Iâm thinking weâre not feelinâ it. Not the way Iâd like. Not the way thatâs going to get us off to a *great* start with the school year.
So, enter the article. It neatly laid out six principles that suddenly give me something to hang my conversations with the kids on. I have an angle. A hook. Six of them, actually. I agree completely with the postâs author that these agile principles apply to everything. Even family life.Â
Without further ado, here they are:
The application to our familyâs work? Pretty much the same as it is in the workplace. "The work is in the thinking, not the typing. Brainstorming, talking, even goofing around with team members -- that's all part of it. Sometimes the best ideas and solutions come not from constant, head-down coding but from letting go. It's not 'fingers on keyboards' that count, it's 'heads in the game.ââÂ
Embracing this and really valuing it makes so much sense when it comes to the work we do as a family â whether itâs house-work or home-work. The process of talking about the work, and how weâre going to approach it, is meaningful. It leads to insight. Itâs part of how we get the kiddosâ heads in the game.
The steps of plan, develop, complete, test and release â performed as sprints? This correlates directly to much of what we tackle as a family. We can follow this process as we figure out so many things: what should the screen time policy be this school year? How are we handling getting house work done around home work and football and volleyball (and screen time)? How are the kids handling big school projects as they come along? How is the 8th grader handling test prep this year (because itâs going to take a different approach than last year)?Â
If you think about it, family life includes many different kinds of processes and systems. Acknowledging this, and being intentional about how you plan, develop, complete, test, and release them? A concrete step towards a functional, healthy family life that supports everyoneâs needs and goals.
Do you have kids? Then I shouldnât have to explain this one. Embrace chaos. OR break it down.
Breaking it down works exactly the same way at home as it does at work. Overwhelming? Too many moving parts? Canât get it done? Or even started?
Slice and dice until the work exists in manageable chunks. Then fit the time within which you have to do the work. I see this being a brilliant strategy for the 8th grader to adopt as she faces some big school projects this year.
Embrace the chaos may mean something altogether different in the family setting than in an agile work team setting. But the result is the same: keep asking the questions, breaking it down, and eventually what needs to get done, gets done.
By focusing on capacity â what work the family team can get accomplished â the result is often an increase in speed in getting said work accomplished. As the article notes, focusing on capacity in and of itself often leads to increased velocity (speed):Â âTo increase capacity we use Agile to develop skills, increase knowledge, improve tools, share work efficiently, reduce inefficiencies and reduce waste -- and that helps us move faster.â This applies to families, too.
âDone is a fluid concept.â I canât express how helpful it is to embrace this as reality. In all things in life. If, as a family, we can accept that nothing is ever really done, then weâre one step closer to embracing continual improvement.
Yes, at some point you must put certain things down and say, âThis is done.â But for many things, this doesnât apply. The processes and systems we use to get things done around the house, for instance, really should be in constant flux. The whole point is understanding when a process we set up isnât working, figuring out why, and tweaking so it works better. Involving the kids in this investigation results in improvements that theyâre invested in.Â
âThereâs no such thing as done, thereâs only improvement.â Words to live by.
(Is it weird that my kids use the phrase âdreadful constancyâ with confidence?)
Iâm not even going to paraphrase here, it so aptly applies to the family team. Straight from the article:Â
"In doing the work, we learn about doing the work. We all do different work, and there's no real âright wayâ to make products, or to make products work perfectly. You have to do your own agile. You have to find your own way, what works for your company and your projects and your teams. But what you'll find, what agile will prove to you, is that prevention is better than correction. That constant iteration is better than getting all the way to the end and realizing you've failed.â