Our work model as a digitization team for our clients

Today we will focus on explaining what the Software Factory working model is, how it is implemented and if it is effective for everyone.

What is the Software Factory working model?

For years, at Possible we realized that many of the main day-to-day problems with our clients came from two factors:

• Impossibility of making changes in the scope and / or functionalities of projects once started
• Impossibility of changing deadlines and dedicated resources to grow the project once the price and deadlines are closed.

In general, it all comes down to a flexibility problem. After attending several courses and some tests with trusted clients, we have ended up implementing a different model. This model is based on agile methodologies that allow the scope and objectives of a technological product to be changed and pivoted as it develops.

The software factory model was born that allows our clients to have a team of professionals with a partial or total dedication to their company . This team is multidisciplinary and covers all technical and organizational needs to be self-sufficient and solve problems that may arise in a project. With this team, 2-week work plans are organized to carry out a series of tasks and deliver value at the end of that period. As time progresses, every 2 weeks you can reorganize the work, change the scope and also month by month you can expand or reduce the dedication of the team to tackle more work or reduce it.

Today we will focus on explaining what the Software Factory working model is, how it is implemented and if it is effective for everyone.

What is the Software Factory working model?

For years, at Possible we realized that many of the main day-to-day problems with our clients came from two factors:

• Impossibility of making changes in the scope and / or functionalities of projects once started
• Impossibility of changing deadlines and dedicated resources to grow the project once the price and deadlines are closed.

In general, it all comes down to a flexibility problem. After attending several courses and some tests with trusted clients, we have ended up implementing a different model. This model is based on agile methodologies that allow the scope and objectives of a technological product to be changed and pivoted as it develops.

Based on this philosophy, the software factory model was born that allows our clients to have a team of professionals with a partial or total dedication to their company . This team is multidisciplinary and covers all technical and organizational needs to be self-sufficient and solve problems that may arise in a project. With this team, 2-week work plans are organized to carry out a series of tasks and deliver value at the end of that period. As time progresses, every 2 weeks you can reorganize the work, change the scope and also month by month you can expand or reduce the dedication of the team to tackle more work or reduce it.

How do we implement it?

Generally our clients begin by carrying out a turnkey project, with a closed scope, price and times, but as the product takes shape and more in In the context of change we are experiencing, it is clear to move to a more flexible model.

Our task is to show the client that one model is not more expensive than another, indeed, the software factory model is generally cheaper, because in a project closed, each change must be budgeted and charged in bulk, while in the software factory model, changes can be scheduled every 15 days and pivoted so that the team focuses on new functionalities or modules that have emerged in conversations with customers or that the market demands.

When he manages to reach a team, a one-month test is launched, and from then on, few customers do not value it positively and decide to continue with this model. The team can be in development or maintenance, design and work on upcoming product updates, or suggest security fixes and enhancements to implement in the application. In the end, the client has the feeling that they have a team that works as if it were their own but organized by Possible.

Is it valid for everyone?

We import this model from companies outside of Spain, especially from the UK, USA and Helsinki where we work with companies that no longer want to work in any other way.

In Spain it is already starting to work and more and more companies are looking for this type of format and not closed projects. It is true that it is necessary to establish a certain trust between companies to be able to work under these models and that the first idea of ​​our national clients is to do a project with a closed price and scope. It’s a good starting point and from there you can get to the software factory model.

We hope and wish that this will be the working model in the future as it facilitates the organization of resources and technical professionals, reduces stress and problems in deliveries. and schedules and allows project leaders flexibility to speed up or slow down development and prioritize some tasks over others.

How is this controlled?

Generally it is important that the team has a Project manager or Product Delivery Leader. He is the person in charge of ensuring that the agreed scopes are met for every 2 weeks and that deliveries are made correctly and that the protocols and validation processes with the client are complied with. It always helps that on the client side there is a profile of Project manager or product owner who sets priorities and knows the business.

To learn more about how we work, we recommend that you see our post on The roles of the Scrum methodology , of the that Possible is nurtured.

What do you think of the Software Factory working model?

Do you know of a better work model or one that you like better?

As always we await your comments.