Dedicated bug-fix teams are quite common in software organizations and are formed for many reasons. Key drivers include a major product release, an influx of new customer sign-ups, or event-based usage spikes that may generate higher volumes of customer issues that subsequently need to be remediated.
Of course, most talented engineers & product people tend not to want to join dedicated bug-fix teams or stay on them for long periods of time.
It might be helpful if we look at some of the typical reasons why this might be the case, in order to develop a competent and effective bug-fix…
Through the drizzling rain I can see him digging away in the front yard with his pick-axe. At 74 he seems old now, and more than a little grizzled. But he still persists in his work despite the weather and his many aches & pains.
For some reason manual labor has always been an enjoyable pastime for my father. Growing up it almost seemed like he relished in it.
I was always in awe of his ability to turn hard work into something fun. …
For organizations looking to augment their technology workforce through an outside partner, developing strong strategic relationships is key to sustained delivery of high quality software over a long period of time. For example, in digital transformation efforts.
Alternative approaches to the long-term partnership approach include the body-shop model, which is more transactional in nature, but works for certain types of organizations & specific types of initiatives. I’ll address that topic in a separate article.
The focus here is on the key considerations when developing deep relationships with an outside software engineering or resourcing firm that you intend to heavily rely…
Why is Tenant Isolation Important?
Building your software ecosystem with tenant isolation baked into the architecture ensures that your business won’t suffer from a cascading compliance or security issue. It can also give your organization flexibility in terms of customizing your solution or services for specific market segments or product tiers.
Where to Start
First and most importantly, establish your requirements for tenant isolation by clarifying the needs of your customers, customer segments and market. Understand the compliance and security profiles & personas of your customers and how many need varying levels of isolation. …
Large software systems that have been around for a while can be notoriously difficult to modernize.
These applications can be decades old, serve millions of customers, be built on top of multiple technical stacks, have huge code repositories, and can be burdened with a significant amount of technical debt accumulated over the years.
Most initiatives that attempt to rebuild these systems from scratch are expensive, have significant slippage, create customer retention challenges, don’t deliver the business or customer value originally envisioned, and are often prone to cancellation midway through.
Most businesses should avoid these “from scratch” efforts, but these kinds…
Over a year-long period of running Product, you might make hundreds or even thousands of both big and small decisions around what, when, and how you deliver certain pieces of your product roadmap.
Somewhere between the Product Team, Engineering, Sales, Customer Support, and the Business there will be a tremendous amount of horse-trading as you optimize your product delivery roadmap in real-time while observing your customers reaction to new releases, the performance of sales, changes in the market, how your customer support team is coping, and if your engineering resources are stable.
The decisions you make might include: a) pivoting…
So you’re running engineering and wondering if your team is any good. The fact that you’re thinking about this is good news.
Assuming a team can deliver even if they’ve done so in the past is probably a bad idea because teams, products and businesses evolve and change over time.
As the person in charge you might be asking:
“Is my team highly performant in the business and if not, where are the gaps?”
With that question in mind, let’s take a look at some of the hallmarks of great engineering teams.
These are 10 indicators of successful teams:
Technology leader scaling software, teams & business. Amateur mechanic. Book junkie. Enthusiastic garage gym owner. Connect with me on Twitter @bscalable