Mboroga Horn Consulting

There has been a marked reduction on the number of testing roles out there over the last couple of years, but this isn't because less software is being written.

🟣 Does that mean that Shift-Left is actually working, with development teams testing their software sufficiently before releasing it? We can hope, but I doubt it.

🟣 Does this mean that more issues are being caught through CI/CD? I am sure there is some truth to this; automated testing is more likely to catch obvious regression than manual testing because it is less prone to human error - as long as it is properly maintained.

🟣 I think what it does mean is that organisations now feel more confident in their development processes. And yet bugs still make it through to production...

This is where Quality Assurance is just as important as it always was, maybe even more so given the complexity of so much software these days.

🟢 If you have got your development and release processes nailed, then it's time to make the small changes likely to have the biggest impact on the quality of your releases. It is time to focus on your requirements.

🟢 If your processes use documented requirements then implement SMART, INVEST, 7-point checks, 5-Whys etc.

🟢 If you follow agile ways of working then introduce regular reviews of backlog items, only starting development when everyone is agreement on what the task requires. 3-Amigos is a great technique to follow.

🟢 Using a hybrid approach? Then pick the bits from above that work for you, just don't do anything for the sake of it. Everything should add value.

I say it a lot, but Software Quality is everyone's responsibility. Get buy-in from BAs, Project Managers, Product Owners and End Users and you might just see those production bug numbers come down even further.

The image? Nothing to do with my post. One of the bunches of grapes we have on our grape vine this year. Fingers crossed we'll have a reasonable harvest.

Is it just me or are you suffering from acronym confusion too?

Yesterday, I saw a post in my feed where an individual was asking for help with EDI...

Now, to me EDI means Electronic Data Interchange, a standardised, secure electronic method of sending orders, invoices etc. between parties. It's beginning preceded the Internet as we know it and relied on protocols such as X.400 to transfer the data over private network connections.
Basically it was a vital component in getting data from A to B before the Internet became ubiquitous.

Reading that post just a little further down, and seeing one of my connections replies, I soon realised they were talking about the "new" acronym, this one being Equality, Diversity & Inclusion.

This got me wondering how many acronyms in common use have more than one meaning. Strictly speaking of course, EDI is an initialism not an acronym.

My wife and I are considering starting a new business in a completely different field. As we delve into the process of setting up this new venture, we have come to realise the overwhelming amount of information available online. This abundance of content can be daunting for many entrepreneurs, including myself.

We understand the challenges that come with stepping out of our comfort zones and navigating through unfamiliar territory. We also have many years experience in software delivery. We know it is crucial to choose the right tools and seek expert advice to ensure that processes are implemented correctly from the start.

Having experienced these challenges first-hand, I am now more convinced than ever of the importance of selecting the appropriate resources and expertise to support business growth. If you are an SME seeking to enhance your operations through the integration of new software, feel free to reach out for a no-obligation discussion. We have the knowledge and experience to assist you in making informed decisions for your business.

Image is of Bob The Builder, a popular children's TV character who frequently said you need the right tools for the job.

Struggling to Find Your Data? You're Not Alone!

If you've been in business for a while and rely on computer systems, chances are you've amassed a ton of data. But are you making the most of it with accurate reporting, integrations and automation?

With over 30 years in software development, I've seen first-hand the importance of proper data management. When embarking on a data migration or integration project, clients are often shocked to discover that their data isn't where they thought it was. This can lead to missed sales, inaccurate information, and even payment issues. Not to mention the issues this can lead to when transferring data between systems.

I once worked on a major migration project for a utility company. With in excess of 6 million customer records, they expected to find that a number of customers with outstanding debts with whom they'd lost touch and been unable to collect. What they didn't expect was a similar number of customers with a credit balance, with whom they'd also lost touch!

Is your data entry like a game of bagatelle? Don't let your valuable data go to waste. Let's work together to streamline your data management and unlock its full potential.

Contact me today to ensure you're making the most of your data!

Are you about to introduce new software into your business? Then STOP!

⁉️ Think about what problem you are solving with the new software.

⁉️ Think about how to transfer existing data into the new system. Now is a good time to improve data quality.

⁉️ Think about how your business currently operates and the impact a new system might have.

⁉️ Think about how it will interoperate with other systems.

If you don't have clear answers to all of these then we can help. Contact us today for a no-obligation chat and get your transformation project off to the best start, bringing you

✔️ Shared clarity of the reasons behind the change

✔️ Continued access to historic data

✔️ A team that understands and supports the changes

✔️ Smooth transition for you and your clients

Due to the success of the Toyota Production System (TPS) and its influence on lean practices, there is little wonder that Japanese words are used to describe key concepts. I want to focus on the use of these lean practices in software development.

"Nemawashi" (English: Laying the groundwork or foundation)
In Lean manufacturing Nemawashi is the first step in the decision making process. It is the sharing of information about decisions that will be made, in order to involve all employees in the process. Nemawashi allows changes to be carried out with the consent of all parties.

In agile software development this is equivalent to the foundational process of understanding requirements, converting value increment ideas into actionable tasks thoroughly understood by all parties.

My favourite process for achieving this is "3 Amigos" where customer, developer and tester all work together to refine a backlog item into tasks.

image courtesy of tanoshiijapanese.com

Due to the success of the Toyota Production System (TPS) and its influence on lean practices, there is little wonder that Japanese words are used to describe key concepts. I want to focus on the use of these lean practices in software development.

"Gemba" or "Genba" is the Japanese for the place where the real work is done. Interestingly it also means "crime scene"! In Lean, it is the factory floor. Lean practitioners undertake regular "Gemba Walks" to observe how production is actually done and identify where improvements should be made. Those making the Gemba Walk are encouraged to use all of their senses and ask questions. The operator on the factory floor is also encouraged to explain what they are doing and why.

Gemba obviously has a corollary in agile software development. The production line is the backlog, user stories, tasks, CI/CD etc. The operators are the customer representative, developers and testers working to produce a product increment.

In this corollary, the Gemba Walk is the inspection of continuous feedback between customer, developer and tester. Everyone in the team should be constantly on the lookout for improvements, asking questions and responding to change.

It fits nicely with my mantra of Quality is everyone's responsibility.

Due to the success of the Toyota Production System (TPS) and it's influence on lean practices, there is little wonder that Japanese words are used to describe key concepts. I want to focus on the use of these lean practices in software development.

"Poka-Yoke" is made up from two words that is usually translated as mistake or error proofing.

In lean manufacturing this is achieved for example, by ensuring that connectors can only be assembled one way around - eliminating the chance that it could be assembled incorrectly.

In agile software development, this is the use of "Jidoka" (autonomation - I'm going to stick with it, see my previous post 😀 ) and CI/CD, to ensure that every task progresses in the same way and work items are in a known state at all times.

It should include environment and data set up as well as code deployment. Feedback should be used to improve processes.

Due to the success of the Toyota Production System (TPS) and it's influence on lean practices, there is little wonder that Japanese words are used to describe key concepts. I want to focus on the use of these lean practices in software development.

"Jidoka" is the principle of automation with a human touch, aka autonomation. See the post image for an explanation of how TPS adapted the original kanji.

"Jidoka" is particularly apt for agile software development because in the concept, a process is devised and then monitored to see where defects occur. Tests are put in place to stop the process when to defect occurs again and the whole process can be modified once a root cause has been identified.

In agile software development there is no time or need to automate tests for every line of code, instead effort should be spent automating tests for the areas known to be most likely to fail, such as integration points and complex calculations.

Perhaps we should start talking about autonomated tests?

My Monday mornings until July... Not as easy to get up at this time as it used to be!

Taking a couple of days out from chasing business to visit my sister in South Wales. Beautiful shot of the castle.

Today we're launching updates to our website and marketing our IT consultancy services to local businesses.

Please share.
Thanks,
Mike