The DIY movement in IT – what does it take to succeed ?


A few days ago, my friend Frank Scavo wrote about the pendulum starting to swing from commercial software to custom built software .  Today morning, I listened to his podcast with another common friend Den Howlett .

black claw hammer on brown wooden plank
Photo by Pixabay on Pexels.com

I would highly encourage you to read Frank’s blog and listen to the podcast. The movement to DIY is real and I am seeing it in the field too. It is something I have wanted to write about and now is as good a time as any. I would like to focus on just a few aspects I have seen as critical to the success of custom building software at scale.

Do you have the right BRAND  to attract the top engineering and product talent ?

There are not a lot of talented software engineers to begin with. Attracting those few good people – be it a fresh CS grad or a veteran developer or product manager – to your company takes a lot more than throwing a lot of money at the problem. Your company may be the best retailer, or bank or automobile manufacturer on the planet.

Do these engineers you are trying to hire know of you as a place that works on cutting edge technology – and all that comes with it like great techies as your colleagues, modern work spaces, a thriving tech community and culture , cool perks and so on ? Do you have credibility in the market as an employer who invests in training people to keep up with the changing market ? Building that brand is real hard work and it takes significant time and investment . It is not a commitment you can make lightly.

Do you have the endurance to move from a project culture to a product culture ?

I have already posted my misgivings on IT shops using agile and scaled agile , so I will spare you those here. But in general – what sets apart professional software shops and rest of the world is the focus on products as opposed to projects. That is a culture shift that won’t happen without a lot of painful – and continuous – change management effort. Hiring has a direct influence on the culture .

The two largest pools of talent are other IT shops (commonly people jumping for better roles and $$) and SI companies ( commonly people who may even be willing to take a small pay cut if need be, but want to get out of their road warrior lives)  – both largely made of people who come from a project oriented background. May be ten years from now, this won’t be an issue – but today it is a definite issue.

One more thing while we are at it – If your team is global, are you willing to make the remote teams self sufficient and fully empowered and not just order takers from HQ  ?

Will your cutting edge team have the staying power?

If you are modernizing your IT function to enable a largely DIY culture – your economic model will probably need teams to be self sufficient on dev and ops, as opposed to one team having all the fun developing cool stuff and another doing the grunt work supporting it and answering the pager.

Will your software engineers hang around long enough if they are woken up at 3 AM by their buzzing pagers ? Do they have the skills to continuously automate ( the SRE types ) ? As you build follow-the-sun teams across the world – will your engineers have the skills and patience to work with people who are across time zones ? As you become more geographically distributed – will they be ok being further removed from the users for whom they are building software ?

Do you have a stress tested strategy for talent pipeline and IP protection?

Just as you want to build an awesome team, your competitors want to do exactly that as well . It is a lot cheaper to pay more $$ for your top tech talent than identifying them early and grooming them for a long time. Even if you are an amazing employer that checks every box, you have to assume a certain level of attrition.

Hence there are questions to answer about the supply chain for talent all the way from entry level to top levels in every geography that you operate. If there is anything more painful than attracting top engineers – it is in recruiting a top notch tech recruiting team and letting them do their job (often radically differently than what you have done traditionally).

Can you balance fun and discipline in engineering ?

Software development is not traditional engineering – developers are more artisans than engineers. On the good side, you will have plenty to choose from their creativity. On the not so good side – only a handful of engineering managers can balance it and eventually ship on schedule. Every good engineering team loves to create and evangelize their frameworks – and what they probably love even more is tearing down everyone else’s frameworks. I am as guilty of this as the next guy or gal.

The battle of frameworks goes like this typically – a new manager notices his teams are using 4 different frameworks . He brings them together and after a lot of debate they agree on a common framework . A few PIs later they find that they now have 5 different frameworks.

Needless to say – you need strong engineering managers, and ideally they are not repurposed from another function to fill a role.

So, can it be done ?

Despite all these uphill challenges – all this can be accomplished and to various degrees I have seen some companies do a decent job with modernizing their IT based on a DIY set of principles. I personally don’t know anyone who is still not struggling with it. The ones doing it better than others are the ones with extremely strong CIOs with the full backing of their CEOs (which is not common), and their boards (even less common).

Book Review : Tim Cook, The Genius Who Took Apple to the Next Level


co71S8XfQdaLpiXPdgVlMg

I bought this book on Amazon Prime to read on a plane ride last week to Austin, and the round trip was all the time I needed to finish it, that too at a leisurely pace. I loved Walter Isaacson’s take on Steve Jobs when it came out and expected a similar in-depth treatment on Tim Cook as well. Considering the fact that Kahney did not get to interview Cook in person, I think this book does as good a job as possible under that circumstance.

I knew very little of Cook’s early years – except that he was an IBMer for a while. The book gives a great view to his upbringing in Alabama and ties together the themes on how his early years influenced his world view quite a bit.

The book paints the picture of a very talented Cook rising up fast at every employer he worked for – and yet never taking the lime light. The contrast is stark – he stayed in the shadows of Jobs when he was COO. And then when he became CEO, he had no trouble dismantling quite a bit of what Steve did at Apple. That takes a lot of bravery given the cult following Steve Jobs enjoyed – even after his death. People I know at Apple have confirmed this time and again that the culture has shifted significantly under Cook to a more pleasant, humane and charitable one.

The million dollar question in every reader’s mind is who has had more influence – Jobs or Cook ? This book makes a good case on why Cook was the better CEO for Apple, based on the financial performance ( which in turn is because of better operations under Cook), more fair employment practices, green initiatives and so on. Cook does not get much credit as a product guy – and only time will tell. His two major initiatives are Apple Watch and the secretive(?) Apple Car projects. Apple Watch has taken off and I bet it will go from strength to strength (already bigger than the swiss watchmaking industry) with the push on healthcare fronts. Car – the book indicates is a failure. If we draw a line today, of course Cook cannot hold a candle to Jobs on product front.

All that said – the book makes a very strong case that Cook is a significantly better human being than Jobs. Jobs had no issue with lying, and he would never apologize for his mistakes. Cook on the other hand have very high standards for himself and he holds his team accountable for that.

As much as Cook cares deeply about Ethics, fairness etc – he is all about the business first and foremost. This becomes clear in the book from the wide gap between his talk on diversity and his actions on filling Apple’s board and senior executive team with mostly white males. He won’t risk disrupting what is in place today. He does deserve credit for significant effort and investment in STEM education and other initiatives to have a better entry level pipeline. Can’t blame him too much though, to be fair – what he has done so far is significantly better than most other CEOs.

While his stance on diversity can be questioned, his initiatives on cleaning up Apple’s act when it comes to their Supply chain partners is commendable. Of course we can argue that Apple can do more and should do more. But on a relative scale – Cook has not only made Apple a better company, I think he has laid the groundwork for the industry to be a whole lot better as a collective. Not a lot of CEOs can claim that !

The book covers in great detail his strong stance on not compromising privacy of his customers – especially with the FBI request for a backdoor entry to phones. That is admirable and is one of the parts of the book that I enjoyed the most. To do this in silicon valley when FB and Google and others all thrive on convincing customers to trade privacy for convenience is beyond admirable. Kahney paints this picture very well indeed.

I would definitely encourage you to read this book

 

 

 

Scaled Agile does not cure the lack of engineering maturity


Scaled Agile has the status of a religion in many tech shops I know. Like with religions – its followers express unquestioned faith, intolerance for other ideas (Waterfall is the devil, EVERYONE should be trained in SAFe), and its praises will drown its criticisms (its not a problem of the framework –  you are just too dumb to use it right) , and a whole branch of philosophical discourse seems to have developed around it ( its a way of life, its a culture, Its a journey and not a destination….) , and people who won’t know a CI/CD pipeline if it slapped them across their face have turned into its evangelists.

accomplishment action adult adventure
Photo by Pixabay on Pexels.com

To be fair – it does work quite well at several software development companies. And on paper, I think it says all the right things. Actually the main diagram on the website is quite comprehensive and thoughtful and I like it. I go back to it when I have to debate my views and its quite useful to remind people on the principles .

My views here are not about the theory – they are just about how I seen it practiced. Now – the trend is “every company is a tech company”. That may or may not be true – but I can say with some conviction that the IT organizations of most of these companies that have embraced SAFe have not figured out how to do it efficiently and effectively.

Let me touch on a few things that are glaringly obvious

PI Planning. 

A good part of SAFe education is about explaining how the process differs from waterfall. But if you look at how it is practiced in real life – especially if you sit through a few PI planning sessions – you most probably will walk away wondering if all that education was wasted. Lot of PI planning sessions scream classic waterfall project planning. While the intention may be to explore “WHY” , the actual sessions usually are debates of “WHAT” and “HOW” – which obviously bleed into the sprint planning and execution too. Also – while conceptually the intention is to agree on goals, in reality most of the agreement is on actions. If you are deciding upfront for next few months – are you truly in continuous discovery mode you set out to do ?

Structure and Process trumps Autonomy and Agility 

Agility needs autonomy. And for a dev team to be autonomous – they need to be close to the people who actually use the product. How many engineers actually even see a real user and know first hand what outcome is best for them ? How many engineers only talk to ONLY their managers and product owners ? How many roles are needed to get SAFe to work – and are they helping or hurting agility in execution ? In practice – most of what seems to happen in the place of “product thinking” is classic project thinking, which is about tasks done within a specified time line. I think SAFe definitely helps with top down communication quite well given it is built with the traditional pyramid in mind. But is it helping back and forth communication with users ?

Deliver on cadence, Release on demand 

This is the part of SAFe I personally like the most. But I very rarely see this happen that way in the wild.  What does happen most of the time is that “deliver on cadence” works reasonably well – and that satisfies management because predictable rhythm helps measurements . But there is little to no ability for a lot of teams to come close to “release on demand”. Its not that teams don’t want to release on demand – but that will need fundamental re-engineering of what was done in the past. It takes time and money and specialized skills – which often don’t show up in abundance . And since rhythm of development is what gets rewarded, the “release on demand” dreams are kicked down the road .

Engineering maturity, or the lack there of 

I think several companies have rushed into SAFe without investing in sound engineering practices first. So while speed might look to have increased overnight – there are a lot of holes to be poked on value generation.

If I am king for a day – I would prioritize instituting solid engineering principles over teaching agile and SAFe. Once you have a strong engineering foundation, Agile works really well. Maybe SAFe will work really well too. But if you don’t have strong engineering capabilities –  all that agile does is to accelerate creation of terrible code that future generations will curse you for.

How do you collect and organize requirements ? If you do a sprint for requirements – then for dev – and finish with a sprint for QA, do you call that Agile or Waterfall ? Just asking for a friend 🙂

In the name of “engineering fun” or just pure incompetence, have you ended up with more anti-patterns than patterns in your code base and now trying to work on making it awesome with SAFe ? Are you comfortable with introducing a shift left culture given where you are ? How is your test coverage – are you certain you are not just testing the same thing ten different ways ? How well do your teams conform to frameworks or does everyone do their own thing in the name of speed ?

In the interest of speed, is Ops compromised ?

The unsung heroes in the tech world are my friends who focus on Operations. A lot of the conversation has always been about how the Dev side of DevOps works. But when the pager buzzes at 3AM – in most shops, it is usually not the developer that wakes up to log on and find what went wrong.

The lack of engineering maturity expresses itself perhaps the most strongly when apps fail. You cannot stop technology from failing – but you can and should be able to minimize the impact and make it easy for users to not be affected for too long. That cannot be an afterthought – it needs to be designed for upfront and operational sturdiness has to be a first class citizen for all development. What is the reality in how backlog gets managed – where do you find “observability” in the list ?

Where to from here ?

I started this as a rant on SAFe – but I think the solution is not about a focus on doing SAFe better. I firmly believe a “back to engineering basics” is where the most value is for most companies. Once you have a grip on that – I think the execution methodology will take care of itself for the most part.