Blogs

Stories, lessons and research from the WorkingMouse team on legacy modernisation, AI, and delivery.

Browse latest articles Browse latest articles

Latest Articles

Browse the most recent thinking from the WorkingMouse team across modernisation, AI, delivery and more.

Owning your software’s intellectual property (IP) is crucial for full control over its use and distribution. Copyright law ensures that, unless explicitly stated in a contract, developers or companies retain ownership of the software they create. By securing IP through employment and service agreements, you gain exclusive rights to make copies, publish, adapt, and commercially license your software. Without this, you risk losing control over your product, limiting its potential revenue or resale opportunities.

In 2024, a traceability matrix offers a more insightful approach to software testing than traditional code coverage. While code coverage measures the percentage of lines tested, a traceability matrix maps tests to specific features, ensuring all requirements are covered and prioritized. This tool provides better visibility into the health of an app for product owners, clarifying which features need attention and improving overall test management. However, it requires consistent tagging and attention to test quality to be fully effective.

In 2024, software project success hinges on mitigating six key constraints: budget, customer satisfaction, meeting user requirements, quality, risk, and time. AI and DevOps are now central in optimizing project timelines, budget estimation, and quality assurance. Enhanced user engagement, automated testing, and improved cybersecurity measures have refined the development process. While challenges persist, incorporating cutting-edge technologies has improved risk management and project success rates, fostering stronger relationships and better outcomes in software and IT projects.

Technology Readiness Level (TRL), initially developed by NASA, is hardware-focused and assesses technological maturity across nine stages, making it less applicable to software development. Investment Readiness Level (IRL), designed by Steve Blank, helps startups gauge market fit and business viability but can be too broad for specific cases like app development. Both models provide valuable frameworks but require adaptation for fields like software and co-creation. In 2024, as technology evolves, more domain-specific models are needed to guide development and investment decisions effectively.

This guide breaks down 12 key software development terms to help you navigate your next project. It covers essential concepts like platforms, technical debt, APIs, product ownership, and project management methodologies (agile vs. waterfall). It also explains the difference between a Proof of Concept (POC), Minimum Viable Product (MVP), and full product development. Understanding these terms will equip you to better manage your software project and ensure a successful outcome.

David Burkett, Head of Growth at WorkingMouse, joined REDD’s Business and Technology podcast to discuss key aspects of custom software development. He covers whether it’s worth building custom software for your business, the development process, hiring in-house vs. outsourcing, and the challenges of offshoring. David also touches on the pros and cons of custom-built software. Watch the full clip for his insights and feel free to reach out to him on LinkedIn or through the contact page!

Artificial Intelligence (AI) raises philosophical and ethical questions, especially around its deep learning capabilities, which mimic human brain processes. While AI’s potential for efficiency is significant, concerns about bias, unintended workarounds, and the ability to switch off autonomous systems remain. As AI evolves, ongoing discussions and research aim to mitigate risks and ensure safe advancements. Though these technologies are still in early stages, we must prepare for their future impact.

Building software in 2024 comes with various risks like scope creep, productivity issues, employee turnover, technical challenges, and external factors. Mitigating these risks involves clear communication, effective planning, and using agile methodologies to stay on track. Employing the PRINCE2 Risk Management Approach—identifying, assessing, planning responses, implementing, and communicating—helps manage risks proactively throughout the project. By preparing and monitoring these risks, you can ensure a more successful software development process.

Jörn Guy Süß, Head of Research and Development at Codebots, recently spoke at the WorkingMouse office about his presentation at the 2022 MODELS Conference in Montreal. MODELS is a leading conference on model-driven software and systems engineering. Jörn discussed his paper published in the International Journal on Software and Systems Modeling, which highlights the shift from unreliable manual model-driven workflows to modern, repeatable processes using advanced frameworks. His talk delved into the relevance of continuous integration (CI) in model-driven engineering, challenges in applying CI to models, and solutions such as reusing the Ant build system.

At WorkingMouse, we focus on the Four Golden Signals—latency, traffic, errors, and saturation—to monitor and optimize system performance. These metrics, part of Site Reliability Engineering (SRE) practices, help us maintain stability, identify issues early, and enhance user experience. By integrating these signals into our DevOps reports, we ensure high reliability and performance, prevent downtime, and support effective resource management and security.

Software modernization involves several risks including data migration challenges, integration issues, security vulnerabilities, budget overruns, user resistance, and downtime. Effective risk management requires careful planning, thorough risk assessments, and transparent communication. At WorkingMouse, we address these risks using the PRINCE2 framework for structured project management, ensuring proactive handling of potential issues. We implement phased rollouts, rigorous testing, and maintain detailed documentation to mitigate risks and ensure a smooth transition.

Kubernetes (K8s) is an open-source platform that automates the deployment, scaling, and management of containerized applications. It simplifies operations by providing consistent environments across different systems, automating deployment and scaling, and offering robust features like self-healing and rolling updates. Prior to Kubernetes, applications were manually deployed and scaled on physical or virtual servers, leading to inefficiencies. Kubernetes enhances modern app deployment with benefits such as portability, automated operations, and security. At WorkingMouse, Kubernetes is essential for streamlining development processes and enabling advanced integrations, supporting continuous innovation and efficiency.

Jidoka is a methodology that combines automation with human input to boost software quality and efficiency. It uses models and pipelines to streamline development and emphasizes early risk management, non-functional requirements, and continuous improvement. WorkingMouse applies Jidoka principles through AI tools like Codebots to enhance productivity and collaboration. For more details, see our blog on Jidoka.

Codebots is our proprietary tool that revolutionizes software development by integrating model-driven engineering, augmented intelligence, and DevOps. It automates coding tasks, streamlines operations, and boosts productivity, enhancing cost-effectiveness and resource use. Codebots supports large-scale modernisation and digital transformation, aligning with our ‘Jidoka’ methodology to balance automation with human input. It offers flexibility, prevents vendor lock-in, and has recently advanced to its fourth generation. For more on how Codebots drives innovation and efficiency, visit the Codebots website.

WorkingMouse has achieved ISO 27001 certification, underscoring our commitment to top-tier data security and reliability. ISO 27001 is a global standard for information security management, ensuring the protection of data, compliance, and risk mitigation. This accreditation enhances customer trust by demonstrating our rigorous security practices and adherence to high standards. For more details on our commitment to security, check out our ISO 27001 certification announcement.

Legacy systems can pose significant cybersecurity risks due to outdated technology, lack of vendor support, and insufficient security features. These systems often face challenges like security vulnerabilities, obsolete authentication methods, and inadequate monitoring. A practical solution is the like-for-like replacement, where old systems are replaced with updated versions that perform the same functions. Additionally, future-proofing strategies, such as risk assessments, data preservation, cloud solutions, and regular audits, are crucial for maintaining security during the modernization process. For more on how we handle legacy system upgrades, check out our work with the Department of Defence.

WorkingMouse was honored as a finalist for the "Putting Queenslander's First" Award at the Buy Queensland Supplier Awards. This recognition highlights our commitment to local employment and community support through initiatives like hiring local talent and investing in Queensland suppliers. The Buy Queensland initiative, which has significantly boosted the state’s economy and created thousands of jobs, aligns with our values of enhancing local tech solutions and workforce. We’re proud to contribute to Queensland’s growth and look forward to further supporting the state's economy and local businesses.

Low-Code Platforms and Internal Development Platforms (IDPs) each offer unique benefits. IDPs provide high control and flexibility, ideal for complex, customized solutions requiring extensive coding by skilled developers. In contrast, Low-Code Platforms enable rapid development with minimal coding, making them suitable for simpler projects and quick prototyping. WorkingMouse's Codebots, an IDP, combines automation with customizable code for both speed and flexibility. Choosing between Low-Code and IDPs depends on project complexity, skill levels, speed, and customization needs, and sometimes integrating both can be the most effective approach.

In today's world, safeguarding information and ensuring business continuity is crucial due to rising security breaches, with estimated risks reaching USD 5.2 trillion between 2019 and 2023. An Information Security Management System (ISMS) helps protect sensitive data and ensures business continuity by systematically addressing security risks. ISO 27001 is a key international standard for establishing and maintaining an ISMS, offering a framework for documentation, audits, and continuous improvement. It provides benefits such as data protection, regulatory compliance, business continuity, and adapting to emerging threats. ISO 27001 is crucial for any organization, regardless of size or industry, to manage cyber risks effectively and maintain information security.

At WorkingMouse, we use Codebots, our proprietary Internal Development Platform (IDP), to modernize and optimize software systems by integrating Model Driven Engineering (MDE), traditional development, and DevOps practices. Codebots enables stakeholders to collaborate on system models, which are processed to generate application artefacts. The process involves committing models to Git, automating quality control, and using CI/CD pipelines for continuous testing and deployment. The resulting applications are tested, accepted, and then released to production. Codebots supports both technical and non-technical stakeholders, facilitating ongoing system operation and enhancement. This approach offers a comprehensive framework for effective software modernization and management.

Platform engineering, or Internal Development Platforms (IDPs), is crucial for modernizing enterprise software delivery by enhancing developer productivity and accelerating application deployment. IDPs offer integrated tools and automation to simplify development tasks and manage complexity. Codebots, WorkingMouse's IDP, exemplifies this by combining model-driven engineering with DevOps practices to streamline development and ensure high-quality software. Similarly, Backstage.io, developed by Spotify and now part of CNCF, improves developer experience by centralizing tools and documentation. Both Codebots and Backstage.io highlight the importance of platform engineering in driving innovation and efficiency in software development.

WorkingMouse has developed a structured Agile methodology called the Way of Working to ensure consistency across project teams (Pods). This process breaks projects into five stages: Brief, Scope, Development, Environments, and Support, blending these stages for iterative improvement. The Way of Working is continuously evolving based on new insights and lessons learned, so keep an eye out for updates.

Part 2 of our series on The Design Conference 2023 highlights the ongoing influence of place and cultural identity in design. Tyrone Ohia emphasises enriching designs with cultural depth, while Evi-o stresses the importance of respectful cultural representation. Reflecting on these insights, WorkingMouse's reimagined core value, 'Connection with Empathy,' draws inspiration from Indigenous songlines and spirals to represent the interconnectedness of people and land, underscoring the importance of cultural respect and unity in design.

This article outlines our manifesto and journey in software development. Our mission is to lead globally in software applications through innovation, emphasizing the value of people, processes, and tools, now also incorporating education and support. We've refined our team structure to include cross-functional squads for optimal project output and quality, and we emphasize the importance of balance and continuous learning. Our processes are adaptable to customer needs, and our proprietary tools like Codebots drive our innovation. Ultimately, we aim to leverage our expertise to empower partners and excel in digital transformation.

This June, we attended TDC at Brisbane Powerhouse for an inspiring 3 days. The conference featured creative professionals sharing their journeys, with a standout didjeridu performance by Tommy of the Jagera people. The theme of AI in design emerged prominently, with discussions on AI as a collaborator and the responsibility of designers to shape the future. Key takeaways include AI's role in enhancing productivity and vulnerability, and the impact of consumer choices on corporate responsibility. Stay tuned for part 2 for more reflections!

Setbacks are inevitable, but they offer valuable lessons that can drive improvement. By analyzing past experiences, we can avoid repeating mistakes, enhance productivity, foster innovation, and share knowledge across teams. Key lessons from our recent workshop include: using the right tools for the job and staying open to learning new ones; prioritizing functionality over perfection in software development; making products easy and engaging to use; and testing early and often to catch issues before they become problems. Additionally, gathering and acting on user feedback, simplifying XML management with annotations and validation, keeping business logic separate from database calls for modularity, debugging by starting with simple solutions and considering broader impacts, coding with performance and scalability in mind, and reviewing past lessons before starting new projects are all crucial. At WorkingMouse, we capitalize on shared knowledge through interdisciplinary teams and a dedicated repository, ensuring we continuously improve and innovate.

The 2023 BiiG Festival - Innovation for Impact featured dynamic discussions on how innovation can create positive social change. On Day 2, highlights included engaging youth in policy decisions, telehealth advancements for rural areas, the development of the Injury Code Assistant, the Disaster Impact Survey, future employment pathways for youth in Logan, and the Queensland Digital License Application. Key themes included the importance of collaboration, technology's role in fostering innovation, and the challenges of implementing change. Stay tuned for our breakdown of Day 3 for more insights from this exciting event.

We recently attended the 2023 BiiG Festival - Innovation for Impact, a multi-day event focused on how innovation can drive positive social change. Highlights from Day 3 included insights from key speakers on responsible technology, including AI, and the significant changes Queensland will face as it prepares for the 2032 Olympics. Dr. Catriona Wallace emphasized the need for responsible tech and learning about innovations, while Cle-Anne Gabriel, Mike Kaiser, and Nicholas Davis discussed shifts in work, productivity, and tech regulation. Dr. Jordan Nguyen concluded the festival with inspiring ideas on inclusive technology and its potential to improve lives. Overall, the festival underscored the importance of ongoing learning and adaptation to harness technology for good.

Jidoka is a software development methodology that emphasises automation with a human touch. Its objective is to enhance and elevate the quality of a software project by leveraging models and pipelines. It is different from other methodologies such as Agile, Scrum, Kanban, and DevOps. Jidoka is a holistic approach to software development that optimises the balance between efficiency and effectiveness. The article discusses how Jidoka can be used to tackle software projects and how utilising the concept of Jidoka within an organisation can allow it to thrive.

When deciding between using a web app or Excel, consider the needs and scalability of your business. Excel works well for small-scale tasks, but as collaboration and complexity grow, its limitations become evident, particularly in terms of version control and security risks. Web apps, on the other hand, provide better integration, automation, and scalability, offering solutions that can handle multiple users and evolving business needs. With low-code and no-code platforms, businesses can transition from Excel to more robust web apps without heavy investment, making web apps the smarter choice for growing organisations looking to streamline operations and enhance efficiency.

Codebots has launched a new course called BotCamp, which we use to onboard our development teams. The four-week course, led by experts, covers model-driven engineering, augmented intelligence, and the Codebots product suite. It is now available to the public in Australia, Indonesia, Turkey, Brazil, and the USA. For more details or to register, visit the Codebots website.

WorkingMouse has been recognized as one of Australia's top custom software development companies by Clutch for the second consecutive year. This accolade reflects our commitment to delivering exceptional solutions and our clients' positive feedback. Located in Milton, Brisbane, our team is dedicated to tackling complex problems and continuously improving. We’re grateful for our clients' support and proud of our talented team. If you’re interested in working with us, feel free to reach out!

Visual aids help communicate abstract concepts more effectively, especially for visual learners who make up about 65% of the population. In software development, visual techniques like T-Shirt Sizing, Fibonacci sequencing, and Poker Cards can simplify project estimations. These methods help convey the size and complexity of tasks, making it easier for Product Owners to understand and prioritize work. Using a combination of these techniques ensures more accurate and meaningful estimations, aiding in better project management and communication.

Modern technologies significantly impact software development speed. APIs streamline integrations, rapid application development platforms like Codebots speed up coding, and existing libraries and tools save time. DevOps and CI/CD improve efficiency and feedback. While these technologies accelerate development, quality and maintainability remain crucial considerations.

We've just released Version 7 of our "Way of Working," an agile playbook designed to manage software risks and boost project success. This latest update introduces several key changes: a shift to a problem-led approach in the Brief stage for more creative solutions, segmentation of support into Enhancement and Product Success phases, differentiation between Brownfields and Greenfields projects for better adaptation, and a fresh new branding that reflects WorkingMouse's focus. These updates are based on real-world experience and aim to keep the process relevant and effective. You can explore these improvements and how they can enhance your projects by grabbing our latest e-book or physical copy!

WorkingMouse is rolling out its strategy for the 21/22 financial year, focusing on four key pillars: improving customer experience, enhancing continuous improvement, automating technology processes, and advancing career progression. Key initiatives include automating DevOps processes to streamline support and release cycles, increasing internal career growth opportunities, and simplifying customer interactions by reducing the number of contacts. The strategy aims to foster growth for both employees and clients, leveraging lessons from the previous year to refine their approach and deliver better results.

Design reviews are crucial for maintaining the aesthetics and functionality of web and mobile applications. As applications evolve, they often drift from their original design, making periodic design reviews necessary. To conduct a review, set up a document to track issues and recommendations, examine user workflows, check for font consistency and accessibility, ensure color and button cohesion, and evaluate HTML structure. Regular design reviews help keep applications fresh and aligned with brand standards, preventing UI/UX issues as your software evolves.

first, evaluate whether to use off-the-shelf solutions or build a custom app. Next, create a product plan outlining goals, success metrics, user benefits, competitors, and unique value. Clearly articulate the problem your app will solve, and validate your assumptions by interviewing potential users. Formulate a comprehensive business plan, set a preliminary budget, and decide whether to hire in-house developers or partner with an app development company. Engage stakeholders early to align interests, and carefully select a development partner. Finally, keep your MVP lean, utilize analytics for informed decision-making, and conduct thorough user acceptance tests to ensure the app meets expectations.

Discovery issues often increase the number of tasks in a project by about 15%, impacting time and costs. To handle this, acknowledge potential variations, incorporate a 10% buffer in your estimates for discovery, and refine your process based on tracked data. This approach helps manage unexpected changes and improve estimation accuracy.

Defining the problem accurately is crucial for effective software development but often gets sidelined in favor of quick solutions. To address this, we use the Lean UX Canvas, a tool by Jeff Gothelf, which helps teams focus on understanding the problem before jumping into solutions. By detailing aspects like business problems, user needs, and desired outcomes, this canvas improves problem definition and ensures better project alignment. Our adapted version of the Lean UX Canvas further refines this process, helping teams prioritize business and user outcomes to guide MVP development.

Iterations are small, incremental changes to a product that add value quickly and are used to keep products aligned with user needs and market demands. They involve regular testing and minor adjustments, such as UI tweaks or functionality updates. Pivots, on the other hand, are major changes to a product or business model that may be necessary if iterative improvements fail to address core issues or if market conditions shift significantly. Pivots involve comprehensive scoping and can be critical for rescuing or revitalising a product. Understanding when to iterate versus when to pivot is key to maintaining a product’s relevance and success.

Scope creep occurs when project requirements keep increasing without proper documentation or discussion, leading to increased development time and cost. It can derail projects if not managed. To avoid scope creep: 1) Nominate a single product owner to make final decisions on feature changes. 2) Continuously review and track changes in the project backlog. 3) Provide estimates for how changes will impact development time and cost. Preventing scope creep involves staying aware of potential issues, maintaining a project schedule, and keeping the backlog updated.

Scrum and Kanban are both effective methods but cater to different needs. Scrum focuses on structured, iterative planning with set roles and ceremonies, ideal for larger projects requiring detailed planning. Kanban offers flexibility with continuous flow and minimal meetings, suited for support and quick changes. At WorkingMouse, we use Scrum for development and Kanban for support and short-term tasks, leveraging the strengths of both approaches to fit our needs.

Agile project management offers numerous benefits, making it a popular choice for organizations. It enhances change management by allowing quick adaptations through iterative work and team feedback. With priority-driven development, Agile ensures that the most valuable features are built first by organizing requirements in order of importance. Its total transparency through daily stand-ups and retrospectives keeps all stakeholders informed and engaged. Agile also reduces risk by identifying issues early in short sprints, which enables swift re-evaluation and minimizes project failure. The methodology promotes enhanced team collaboration through regular meetings that address blockers and support skill development. Additionally, Agile improves cashflow by prioritizing key features, leading to faster delivery of a Minimum Viable Product (MVP) and quicker market testing. Overall, Agile’s flexibility and transparency help lower risks and deliver consistent value compared to traditional project management methods.

As we closed out the financial year, we took the chance to reflect and strategize for 2020-21. Our company-wide strategy day, led by CEO Matt Francis, highlighted our renewed focus. Our vision is to foster creativity and mastery to deliver valuable products, and our mission is to broaden our horizons through continuous improvement and client value. We have four main goals: 1) Ensure consistent quality throughout project phases, 2) Expand delivery capacity and customer reach, 3) Deliver and measure the value of our software, and 4) Prioritize people in our software development. These goals will guide our efforts as we continue to improve and grow.

Estimating software development costs is challenging due to the unique and evolving nature of software projects. Unlike other industries, software development involves many unknowns and rapidly changing technologies. Methods like bracketing, historical comparison, and scoping approaches such as T-shirt sizes or Fibonacci estimations are used, but accuracy improves with more information and scientific methods. Continuous learning and refining the estimation process can enhance accuracy, but no estimate is perfect.

Agile project management, unlike the traditional waterfall method, emphasizes flexibility and iterative progress, allowing for quicker adjustments and better risk management. It improves product/market fit by prioritizing customer feedback, enhances stakeholder collaboration, speeds up market entry, and optimizes feature delivery. Agile frameworks like Scrum and Kanban structure this approach, with WorkingMouse’s evolving Agile process addressing common issues such as unclear requirements and unrealistic estimates. Adopting Agile effectively requires both a flexible mindset and robust processes.

The length of the scoping phase in software development has a significant impact on development time. Our analysis shows a 90% correlation between scoping time and development length. While longer scoping can potentially lead to more thorough planning and better implementation, it may also extend the overall project timeline. Therefore, finding the right balance in scoping length is crucial to align development time with project goals and market needs.

Proper software release involves not just development, but effective deployment and hosting. Cloud hosting options are either private (more secure, costly) or public (less control, automated, cost-effective). WorkingMouse handles public cloud setups (AWS, Azure) efficiently, reducing setup time from weeks to a day with tools like Kubernetes. Costs for clients are minimized as WorkingMouse covers setup for public cloud environments, while private or customized setups may incur additional fees.

Verinote, developed by WorkingMouse in November 2019, is a secure web app for detailed and confidential note-taking, especially for law enforcement. It automates data recording, ensures secure storage, and includes features like audio recording and handwriting recognition. Built on a LAMP stack and delivered on time and budget, Verinote was completed in six weeks using a fixed time, variable scope approach.

Speed to market is crucial, but adding complex features can extend development time. Key functionalities that increase complexity and risk include offline sync, third-party integrations, advanced security, multitenancy, dynamic reporting, and multi-platform support. At WorkingMouse, we factor in these complexities and associated risks in our time estimates to avoid missed deadlines and budget overruns.

The length of a software development project depends on several factors, starting with scoping, which involves exploring and defining the project’s goals and estimating the time needed. Scoping typically takes 2-4 weeks. Agile development divides the project into iterations (1-2 weeks each) and milestones (which can range from 2 weeks to 3 months). The overall development time varies based on project complexity, scope, and priorities set by the product owner. Small projects may take around 6 weeks, while larger, evolving projects can extend over years.

Show More

Discover how modern software, the right delivery approach, and continuous modernisation can support your organisation.

Government solutions Government solutions

Capability statement Capability statement

Join our monthly newsletter & we’ll plant a tree.

As part of our commitment to sustainability and a greener future, we’re planting trees through Carbon Positive Australia in exchange for your contact details

First Name
Last Name
Email Address
Verify You’re HumanPlease type the characters shown below.
CAPTCHA
Different Image
WorkingMouse logo

(07) 3667 9559

info@workingmouse.com.au

PO Box 1596
Milton, QLD, 4064
Australia

QAssure No. 20247

Quick Links

Services

Newsletter

About Us

Publications

Process

Newsroom

Resources

Contact Us

Careers

Privacy

Government

Speaker Page

Tools

Terms & Conditions

Clutch Review logo

The Glassdoor logo
ISO 27001 Certificate ISO 9001 Certificate ISO 14001 Certificate

Made with ❤️ in Milton, Brisbane (Meanjin) Australia.

WorkingMouse acknowledges the Traditional Owners and their continuing connection to land, sea and community. We pay our respects to them, their Elders, both past and emerging.

Torres Strait Islands Flag Australian Flag Aboriginal Flag
Top B2B Companies Clutch Award 2022 Clutch Top Company 2022 2023 Clutch Award 2018 iAwards 2023 Buy Queensland Finalist Award Award 1 Technology Fast 50 2017


2026 WorkingMouse Pty Ltd. All Rights Reserved.