Workweek 01×02: Mayday!

Workweek 01×02: Mayday!

Monday was a bank holiday. Went to the farm to see lambs. 
Tuesday was my usual day off. Gradually forgetting how to do work. Went to the playground.
Back on Wednesday. Starting to think about the next few months ahead as projects get delivered, and the future opens up. Catch up on emails, and what’s been done on the data fixes I put in place on Friday. Then trawled through the couple of Trello boards I have of planned work and deliveries for next few months with Stefan to see what’s on everyone’s plates. 
Chatted to Obi about data fixes. Looks like they’re progressing well after getting unstuck last Friday. Wonder if there’s a better way of mapping our whole days chain, and how to investigate and resolve issues better. 
Some discussion with Kim on what we could do to make signing up for demos more appealing. Marketing is still something I feel .. I’m not sure what. Interested in, but limited experience (A-Level Business Studies counts?). I wonder what effect 20 years of Internet pseudonymming has on your awareness of how you come across. 
Interrupted to pick up #son1, but making up some hours in the evening meant I could hammer through some email inbox. Reminds me of an article in FT this week about Inbox culture, and the potentially dehumanising aspect of a never-ending stream of emails compared to talking to people, and alternative forms of communication.
Dug back through about a year’s worth of “do this” emails – most of them didn’t really need doing in the end (or not directly by me), but actually it got me to do a lot of reflecting and looking back at where things were a year ago, so not wasted time. Sometimes it’s good to see how far you’ve come, like looking back over a hill ridge as you approach the pub – it’s easy to always look forwards, and always worry about what’s left to do, without ever appreciating what you’ve done already.
Thursday actually a normal day, hours-wise. Sent the emails I’d lined up last night (I don’t like sending mails out-of-hours, think it sends a bad culture signal, so I tag drafts to send with a “morning-post” tag and deal with it swiftly in the morning) and updated my email backlog tracker in Google Sheets. I thought I’d use this originally to .. I’m not sure why, actually. At some point though, I added in the colour-coded comparison-to-average inbox figure, which flags up when I’m above average. By sorting things into to-do (or “action”) and to-reply-to (or “response”) folders, I’ve found I get feedback on what sort of email I need to pick up on. Reversing the trend for “action” emails feels good.
Taking a hefty think about “strategy” for the summer months today. Feels like a big word, but at the moment it’s really a case of working out where each of our product lines is at, and working out what conversations/decisions are needed next, and who/when needs to be involved.
Spoke to Ben at Sussex Uni about a possible “automation anxiety” workshop. Made me think about how a lot of the hype and associated fear is about “robots”, but really it’s lack of control that people fear – but that can manifest as being taken over by robots, algorithms, immigrants, politicians, or even members of staff in the same department. At the end of the day, we like to think we own our own destiny. From a stats perspective, I think there’s some interesting issues that tie modelling the world and data into evidence – based policy, algorithms, and science generally. Public trust in science (or scientists) is a fascinating subject. 
http://ift.tt/2qeK56q(+ how do you insert links in Evernote for Android?) 
Looking at time reports for recent NI product work. Bringing some bureaucracy to the company and asking people to log time 😉 
Friday back thinking through where we’re going. Lots of looking back to our plans 6-8 months ago, seeing what’s changed, and lots of post it notes covering my desk, which always makes me happy. Also generally still feeling my way as a semi-Product Owner, so making up a lot of diagrams (A “Value Flow” sketch? Which bit of my head thought that up?) and quick write-downs of rules and ideas to help guide me through the process. Good fun. Important stuff. Difficult. 
Spent a good amount of time going through various emails and write-ups, distilling into new documents, and going round the team for various status updates on different bits. 
Finished the week with a bit of personal research time, banging the metal so-to-speak by getting back to a command line and trying out some automated phpunit runs, and bash scripting. Get sidetracked into fixing and neatening tests, and pretty sick of PHP error levels by the end of it. But learned a lot, I think? 
Anyway, bit of a dash though this week, and nowhere near enough photos. Maybe nothing but photos next week…? 

Open original in Evernote

Workweek 01×01: Easter Pilot copy

Workweek 01×01: Easter Pilot copy

An attempt to keep Weeknotes. Don’t know it’ll work, but you gotta try. One day I’ll do a proper background note, but sometimes, like this evening, #son1 asks me what I did today, and I give him the boring version to send him to sleep, but it kicks off thoughts on the more interesting version. Not sure which version will turn up here, but I’ll try to keep it punchy and exciting, just like my job is in real life,  I’m sure. 
Monday wasn’t the best week to start a work diary, as I ended up staying at home waiting for the bathroom fitters to come round. In between making coffee and rediscovering the stopcock, I caught up on my two main message points – the email inbox and Slack. I constantly alternate between feeling love and hate for computer-mediated messaging these days, probably depending on how busy on other stuff I am. It’s easy to fall into the habit of feeling like my own secretary once I’m bogged down in the week, and I’ve never worked out a favourable approach to it all, despite numerous attempts and systems. 
Otherwise, just a few minutes in the morning with a post-it, pencil, and calendar help me decide priorities for the week, and what I need to do on each. You can’t do everything in one week, so it’s good to know the really vital points of interception. The post-it note will stay with me in my new notebook – usually I’d use Wunderlist to keep track recently (again, so many systems) but a new pad feels like a good time to start afresh. Again. 
Thinking about it, a disrupted hour at home to start the week is still a useful space to orient myself for the rest of the week. I’m surprised more places (or, indeed, we) don’t make more space for individual planning and agreed “quiet time” for tidying up our own lives. 
After heading into work, I caught up on how our Australia project is going. I find myself increasingly cross-referencing an electronic sprint board with some sort of paper print out (an initial timeline, or a software architecture map, for instance) – maybe there is no single killer tool for organisation, but the best value comes from combining formats and media together. 
Did other backlog checking. A few tech tidies and testing – I tend to be more hands-on when deliveries are looming. Meta-planning meeting  to get our upcoming focuses sorted out, and finally some planning for the last stages of our Neighbourhood Plann support tool. 
Took Tuesday off, as usual. Saw some bluebells with the son. 
Wednesday. Struggling to think of a decent place to meet someone for coffee in Brighton, which is pretty daft considering the number of cafes now. Can’t work out if cafes are getting smaller and noisier, or I’m getting older and picky. Probably both. 
Expecting a bit of a rushed day today, with not just sprint turnover today tomorrow needing various tasks and backlogs tidied up, but also a project or two coming to a head. Tidying up for release anyways takes more time than people realise, and making sure all the right corners are polished is so often underestimated, or even forgotten. 
Feels like you either choose the inconvenience of appointing someone ‘chief finisher’, or the inconvenience of allowing enough flexible time across the team to deal with whatever comes up. I have a theory that chaos can’t be avoided, just moved around between different layers, and parcelled up into different days. 
Spent some time in the morning on dev work, picking up left over testing and mostly playing with HTTPS. Having been away during discussion of this sprint’s tasks, really noticing the difference between what’s in people’s heads and what’s written down. The importance of narrative in task descriptions still feels huge, but obviously only where other communication/shared understanding breaks down, ie where I’m not directly talking to people, or haven’t been part of the conversation previously. This notion of jumping in and out – what does it mean to team elasticity? What is elasticity? – The ability to bring in new people to help out quickly, perhaps. Wonder what the facilitators and barriers to this are.
Backlog priorities with Luke and Flo – Luke’s been picking up our Neighbourhood Plan work and thrown head first into Product Management. It’s a good experience to go through, but Product Management isn’t a role or skill you learn quickly or easily… 
With prep for tomorrow out of the way, I don my stats-code hat and delve into a few data issues we’ve encountered recently. Everyone like to think data processing can be left to the machines, but the complexity of the data we deal with, multiplied by the number of systems we run, mean that there’s frequently something that needs looking into *somewhere*. I like to think of it more like gardening than computing – data, datasets and units of analysis are always growing, and the systems we’ve built allow that growth, but maintenance and “shaping” is still best done by a professional. With powerful data trimmers. 
Anyway, investigations go well and sprint has gone good. Dev Alex is tidying up and working out what needs to be deployed where, but looking good for tomorrow. A few emails, a drop of Limoncello, and time for home. 
Thursday was sprint turnover day, but started with some initial prompting to begin thoughts on how we celebrate our one hundredth sprint in the next few weeks. So the #sprint100 Slack channel is now a thing. 
Our sprint meeting has its own slightly manic culture now and, looking back as we approach our 100th sprint, it’s fun to reflect on how the energy, ambience and “culture” of the meeting has evolved, away from all other work. Some of that comes from retrospectives, some from being human, and so on, but it feels like there’s an almost-tangible boundary between the gathering and “the outside”… 
Some great work being demo’d as project launches get closer and closer – our new site to provide data for Neighbourhood Plan forums is coming together, as is our work to bring the Insight technology to Australian clients. Also great to hear good feedback from clients in our little “Word on the Street” section. Still lots to do, as ever, but progress is good and, importantly, visible. 
The rest of the afternoon mostly spent on data maintenance, and making some minor code architecture improvements as part of it. Feels like the old days when it was just me as The Developer sometimes… 
Friday was a good day. Somehow we largely underestimated our sprint ‘velocity’ yesterday, and burned through a bunch of site tweaks, fixes, releases and associated internal announcements. Nice to end the week before a back holiday on a bit of a high. We even all managed to get out to Cafe Aldo’s for some lunch grub. 
Had a chat with Mike, the Chairman of our Board – just to catch up really, 3 months on from Tom leaving us with the company. My own 1:1 chats have fallen by the wayside a bit, so it’s nice to get some free time to just shoot the breeze with some personal thoughts on life, OCSI and the Universe. 
Well, that’s week one over. Looking forward to reading this back to myself before posting somewhere. A 3 day week next week, so no excuse to skip it, really… 

Open original in Evernote