Everyone wants fast delivery. What you actually want is predictable delivery. You get predictable by working small. When you work small you get more feedback, for your product and your code. Know what happens when you action feedback more often? You get fast delivery.

Full room for @tjridge at #dddadelaide for his talk on How to (remotely) win friends and influence people 🎉

Still in amazement at just how incredible the talk from Kate was today. Story telling, technical detail all top notch, and it was her first time speaking to boot. Incredible #DDDAdelaide

4. Consume By now you might have a bit of a rough idea on the what, find some of the best sources of content to help complete the picture of what it might look like. If you find yourself endlessly consuming, you can stop, that’s probably the thing worth exploring more.

3. Chat with a coach or mentor Chatting through my situation with a coach throughout this process has been hugely beneficial. It’s helped me to test the waters for some early thinking and be reality checked. Little bit by bit you can narrow in on your path

2. Identifying strengths Whatever survey took of choice you prefer, take a quiz to identify your strengths. Whilst it will probably come back with a lot you know, it will be the ones you don’t that might just give you the nudge to try something different or be more ambitious

1. Journalling For a couple of months I made sure to journal answers to the following questions: - what was I jealous of someone else doing? - what excited me? - what gave me energy? This helped me to start surfacing the activities that I really valued

Taking a period to critically evaluate your career path and understand if it’s working for you, your family, and your goals is just so damn important. Here’s some techniques I used to help me to start building better clarity around what I wanted

“Remote collaboration is harder”, of course it is, if you never spend time intentionally creating opportunities for remote staff to get to know each other in and around meetings, collaboration is absolutely going to suffer. #remotework

There’s a lot of push to get remote workers back in the office in the name of collaboration. Yet, most companies pushing this never put in the effort to create that sort of collaboration in a remote context to begin with.

I've been spending some time digging into Rom.rb internals and learning how to leverage its upsert command in an application. I've written a guide for how to write you own custom rom command and handle bulk upsert to boot. https://t.co/21a0jGRBKn

Want to improve your team's decision-making and ability to ship faster? Check out my post on the importance of psychological safety engineering teams. #engineering #teamwork #leadership #agile #softwaredevelopment https://t.co/m9me24Joyu

Scheduling your team at 100% capacity is a great way to ensure that nothing will be delivered on time.

Anything beyond that 6 weeks, if, in the same epic is a good smell you have a # of capabilities there hiding as separate epics, or can just be hand-balled a very rough t-shirt size of 2+ weeks, 4+ weeks etc as a rough guide to factor into your long term roadmaps.

The cognitive load for your team (and you) is reduced here too, by just focussing on those next few weeks and having a generally very rough idea on what the 6 weeks after that might look like.

By slicing up to around 6 weeks worth of work, or whatever minimal runway makes sense for your team, you keep incentivising those small pieces, you don't over-index on planning ,so you can keep yourself flexible for any future change and ditch anything that doesn't work.

What we're trying to do here, ultimately, is mitigate the risks around decisions made with incomplete information.

If you slice too far ahead, you fundamentally end up making decisions based on incomplete knowledge, or knowledge that would be more accurate if you had gone through the process of delivering, that existing backlog of sequenced work.

The problem with story slicing, is knowing when to stop.

As development went on, it became increasingly clear that our stories weren't necessarily as refined as we thought, nor sticking to that desired slice size. This obviously impacted our ability to deliver when we had planned we would.