Categories
Agile Management

The Power of Pause: Breakthroughs from Benching Projects

There are moments in my professional life where I’ve realized I need to take a step back from a project I am working on. This is not an indication of defeat or a sign that I have reached an impasse. In contrast, it’s a strategic decision to let the project rest for a moment, to allow a temporary hiatus. This retreat could last a day, or it might stretch for a month or even a year. The duration is not what’s critical here. What matters is the willingness to shift my focus away, just for a while.

The benefit of this ‘benching’ tactic is that it presents an opportunity for me to later revisit the project with a renewed perspective, a fresh mindset. It’s amazing how a bit of distance can dissolve mental blocks and spur original ideas. Mundane moments such as a workout session at the gym or a long, warm shower become transformative periods where I can subconsciously or consciously brainstorm alternative approaches to the project.

Moreover, it’s not unusual to realize during these intervals that I’m missing a few critical building blocks to complete the project satisfactorily. The advantage of stepping back is that it gives me the breathing room I need to acquire the knowledge I lack or find the missing link that was previously elusive. This investigation period could range from taking a quick online course to going through a stack of relevant texts or consulting with industry experts.

At times, the missing piece might be something trivial – a simple solution that I’ve overlooked. However, there are occurrences where it turns out to be a substantial, fundamental piece of knowledge that I didn’t even realize was essential initially. This realization can be both humbling and enlightening, reminding me of the vast universe of knowledge that exists and the joys of being self-taught.

A self-paced learning journey is indeed a rigorous adventure, full of stumbling blocks and triumphant discoveries. It tests the limits of my patience, resilience, and determination. But it also breathes life into my professional endeavors, infusing each project with a unique sense of ownership and pride. By allowing myself the flexibility to take a step back when needed, I’ve found that I am able to return to each ‘benched’ project with a fresher perspective, renewed enthusiasm, and often a more effective approach to solving complex problems.


Categories
DevOps Internet of Things

Edge Computing has Opened my Mind Beyond the Cloud

Whilst researching how to set up my Raspberry Pi cluster I stumbled across some people across the interwebs who clustered together a bunch of Intel NUCs (Next Unit of Computing).
Why cluster Intel NUCs? You get a powerhouse of a cluster. These NUCs can pack some punch, i7s with 64gb ram… cluster 6 of the 8th gen i7s with 32gb ram and you have 24 cores, 48 threads and a hefty 192gb of ram. All for severely less cost and power usage than some fancy dual Xeon setups. Not to mention they run near on silent and consume comparably low energy needs to run them 24/7.

I don’t have a use case enough to fork out and buy a bunch of Nucs to purely play with this type of setup but was VERY curious to learn an amazing use case in the states.

Enter Chick-Fill-A

Chick-Fill-A is a fast food joint in the land of fast food, United States. Chick-Fill-A uses edge computing in their franchise stores, they deploy a cluster of just 3 NUCs, with instructions so even the least tech savvy owner/operator can plug in the hardware.
Once plugged in the cluster automatically builds itself and launches itself into production.

You can read more about Chick-Fill-A’s Edge Computing setup here: https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at-chick-fil-a-scale-7b0607bd3541
The rest of their blog writings are well worth a read too

The Cloud is Not the Answer?

All of a sudden I realised, migrating everything to the cloud simply cannot be my default answer for an application or service.
Sure, Cloud is by far a better option for many most companies and Chick-Fill-A is no exception. But there are many reasons why a hybrid solution is a great answer to many sticky challenges. Latency and security being some initial benefits. Simplicity in utilising basic hardware for tech-challenged franchise owners at Chick-Fill-A another prime real world example. No doubt there are plenty more.


Next Steps

Learn more about Edge Computing
But also develop my thinking around the merits of cloud computing for all scenarios. I will be looking out for more use cases for Edge Computing, hopefully with some real life examples. Some thinking is needed around further benefits of edge computing over and above latency, security and simplicity also growing a deeper understanding of how I might actually architect a solution.

Build my Raspberry Pi Cluster
For now using the RPIs is a super affordable way to mess around with a cluster setup in a lab type environment. Hopefully it will give me hands on learning opportunities for setting up the hardware, messing around with Kubernetes, probably Docker and I can learn more about elasticity and scaling. Should be a fun project.

Categories
Agile Management

Agile Challenges – The Standup is not a Status Meeting

Stop treating it like one.

A perfect standup:

  • What are you currently working on or about to start.
  • What intermittencies do you have with other people/projects
  • What Blockers or Impediments are you up against.

That’s it. Short, Sharp, Snappy.
The standup is there for your team to work together, not for you to stay in control of everything that is happening. There are better ways to do this.

Your team members have lives

Between the school runs, the doctors appointments, bad traffic or the dog eating your homework, people have lives outside of work. holding your standup at 8:30am is guaranteed to have absentees every other day and you begin to lose the benefits of your daily standup in the first place.

When to hold your standups?

Your only answer of when to hold a standup is to gain full agreement from every member of the team. suggest reasons why we don’t hold them first thing in the morning. then get everyone to agree.
I recommend suggesting times between 10am and 2pm.
Quarter to x is a great time for a standup, people have meetings staring on the hour and makes sure the standups are short, sharp and snappy. Give it a go, and don’t be scared to change time if it is not working for your team.

Holding remote Standups.

I heard a fantastic solution to a fun problem. half of your team is working from home and having differing levels of engagement create challenges of their own.
Enter a simple rule. If one person is calling in remote to the standup, Then everyone is calling in remotely.
This puts everyone on a level playing field and gets the same level of engagement from everyone.

Amazing solution I cannot wait to trial this one out.


When to take things ‘Offline’

A great standup will bring to light issues and challenges that the team need to handle. you need to facilitate this out of the team members, and give them a little time to discuss back and forth the highlights of the issue.
Once highlighted it is time to interrupt, letting them know to take the discussion offline. The great teams I have worked with are great at this and often stop the conversation themselves, keeping the whole standup in flow.

If you find your standups taking longer than 15 minutes, you are probably letting these discussions run away. big waste of time for all other members. Rein it in.

If you need a status update

Perhaps you don’t have an open and transparent workplace/team? Or perhaps your team members are very autonomous, whatever works for you, your team and your organisation. I would suggest working through other methods of getting the status update you require. A short meeting/update in a one on one capacity can often be the best method. this also gives everyone a great opportunity to cover off many other issues at hand, perhaps a disruptive issue or some large blockers or maybe the team member wants to ask for some help or upcoming time off. Standup is not the time for any of this nor is it conducive to people opening up to issues in front of the whole team.

Categories
Agile

Agile Challenges – Sorting The Backlog

There one is a fun exercise I enjoy working through, especially in a newly formed team or project.
“How do we prioritise what is important and thus needs to be at the top of our backlog?”

The number one thing to remember here: Stakeholder Engagement.
You NEED to get everyone who cares (even a little bit) onboard here. Failure to do so might lead to pains down the road. (“What about this feature I think is very important… where is it? ~Forgotten Stakeholder)

Ordering your Backlog

This is a surprisingly fun exercise that really gets people thinking, engages all stakeholders and will give you a rough starting point for a backlog….

Corral all of your stakeholders, make sure you book in time enough for this session based on number of backlog items you have. This might take several hours.

  • Player 1 takes stack of stories and chooses which one is most important.
  • Player 2 takes stack, chooses one and places it on table, either more important or next important.
  • Player 3 takes stack and a. Can rearrange one item to new position on table. Or b. Choose story and place it where they deem important.
  • Player 4 takes stack and repeats this step.
  • Continue passing stack around team until no stories remain.
  • One last round where each team member can rearrange order of importance of ONE story.
Benefits of this Method

This method gets everyone involved, which is important for engagement and ongoing morale, esp for the quiet ones of the group as it gives everyone equal opportunity to promote their opinions. Especially good if you have an alpha type involved.

It also brings up a myriad of conversations about features that we as individuals might have never thought about or considered.

Points to assist in facilitating.
  • Beware of conversation or discussion taking away from the exercise, if you need to interrupt, do so. If you need a quick fire round to speed things up, do so.
  • Make sure you plan enough time. This depends of size of story stack but I almost always find 1 hour is never enough.
  • Make sure you invite important stakeholders in from outside the delivery team. They need to be involved of your product will fail.
Outcomes

At the end of this you should have multiple valuable outcomes.

A rough backlog, in order of importance.

Better engaged team members that valued their opinions being heard.

Better engaged stakeholders that valued being involved in important ceremonies.

And with some luck your team will be another step to working together as one coherent performing delivery team.

Next Steps

The Product owner, in conjunction with the appropriate analysts and key stakeholders needs to review this backlog and validate the value of each story and how it should remain in its place.

Do NOT shuffle the order of this backlog yet. Define the value, understand they why and how.

If you feel this order should be shuffled make sure you communicate this with the whole team involved. Tell them what you are shuffling around and why.

If you don’t do this, they will look at the backlog, see it shuffled, wonder why, reconsider the importance of their own opinions and also start questioning the integrity and trust of the product owners or senior stakeholders, completely undoing all of the hard work you set out to achieve in the first place.

Good luck.