×

Services

When you partner with WorkingMouse, you embark on a journey. Our talented crew engage with you throughout the project build. We guide you through each step in the process. When WorkingMouse engages customers, our flexible services adapt to each step of the journey. We keep any discussion about our services transparent.

The Way of Working maps out each step of the way through the journey. It brings together all our expertise in one place, and describes exactly how WorkingMouse engages with customers.
Book a free consultation
 

Engaging Development and Migration

For businesses, WorkingMouse provides Legacy Migration, in addition to Software as a Service, Mobile and Web application building, and Experimentation for Research and Development initiatives.

Legacy Migration

Legacy software can inhibit business growth. It’s slow, costly to maintain, and less secure than a cloud application. Many businesses bear the cost of legacy systems because of the data stored on the software and its functionality. Our Codebots are experts when it comes to legacy migration as they can identify and write to the existing patterns in the software.

Mobile and Web Apps

Our team has experience developing applications for a wide variety of industries using an agile methodology that keeps our solutions scalable long-term. A benefit of working with us is our Mobile App Behaviour, which deploys Cross Platform Mobile Applications using one codebase. This Hybrid Application lowers technical debt. Using this process, the same app can be deployed as a web application. This empowers businesses to connect with end users on the right platforms.

Software-as-a-service

Legacy software can inhibit business growth. It’s slow, costly to maintain and less secure than a cloud application. Many businesses bear the cost of legacy systems because of the data stored on the software and its functionality. Our Codebots are experts when it comes to legacy migration as they can identify and write to the existing patterns in the software.

Engaging Pods and Squads

When starting on a software development journey, many businesses need a specific skill set to see a project through to the end. At WorkingMouse, a Squad brings together staff with all the skills needed to build an application.

Squads have a designer, two web engineers, two tools engineer, and a squad lead. The benefit of a Squad is that the staff skills sets ensure redundancy across projects. A squad will generally work across two projects simultaneously. 

Project Models
Conducting Estimations
 
Squads and pods are available to hire under time and materials agreements. A single Pod and an entire Squad are both available to hire.

  • If you hire a Pod the skill sets your receive include a web engineer, a tools engineer dedicated to the project full time, and a half-time commitment from a designer, and a squad lead.

  • If you hire a Squad the skills set you receive includes twice the time commitment and staff with two web and tools engineers, and a full-time commitment from a designer, and a squad lead.


Engaging project models

Without thinking and challenging any assumptions about project time and scope, a business opens the door to confusion. After engaging squads and pods, customers receive consultation on the best project model for them, which reduces confusion around time and scope planning.

Selecting a Project Model



WorkingMouse embraces agile development. A part of this methodology is deciding whether project scope and project time are fixed, or flexible. Choosing the correct project model informs the time and material required to complete the project.

If time is flexible, and the scope is fixed, the number of weeks to hire a Pod or Squad varies. Predicting the exact length of time becomes more uncertain. Models of uncertainty and time, like the Cone of Uncertainty, quantify the size of uncertainty at different points of development.

If scope is flexible, and time is fixed, then Pods and Squads deliver the highest value work items within the available fixed time.

Engaging Estimations

To manage risk, WorkingMouse uses a scientific method. Anything that can cause risk is quantified, weighed, and mitigated. With this scientific method, we lower the chance of time and cost growing exponentially.

From the first meeting, when Pods and Squads engage and brief customers, we take the abstract concept of risk, and quantify it into concrete values. They quantify familiarity with the proposed project, and the complexity of the project. Risk estimations are revisited and communicated at key points during development.

Managing Risk


Risk estimations compare complexity and unfamiliarity values. 

Where these two values meet on the table gives an estimate of project time. We allocate extra time for activity and work that supports and maintains development quality. The final time estimate appears in a Scope document for discussion.

During development, each task lined up for development work receives due diligence in a meeting called an elaboration session. Unfamiliarity and complexity are revisited in this elaboration session.

In the event that estimating and revisiting unfamiliarity does not effectively manage risk, a shared risk model guarantees extra development time will not inflate project budgets.

Achieve the extraordinary

Book a consultation