When and why should you bet on dedicated product team cooperation model?

00:00 → 00:03

It takes a team to build a fully fledged digital product,

00:03 → 00:04

but what if you don't have a team?

00:04 → 00:07

I'm Michael and I'm a Senior Business Analyst in Merixstudio

00:07 → 00:11

In this video, I'll elaborate on the dedicated product team model,

00:11 → 00:13

which might be the answer to your needs.

00:13 → 00:16

The dedicated product team is one of the main cooperation

00:16 → 00:19

models used in software development outsourcing.

00:19 → 00:21

Within this kind of collaboration,

00:21 → 00:25

your software partner provides you with a team of experts who

00:25 → 00:27

cover a wide spectrum of roles in your project.

00:27 → 00:31

The dedicated product team model works best for companies

00:31 → 00:34

wanting to build their products from the ground up.

00:34 → 00:37

You may also use it to augment your internal development

00:37 → 00:39

teams' work around scaling up your product.

00:39 → 00:41

It will work just fine as well.

00:41 → 00:44

The key benefits of a dedicated product team are incorporated

00:44 → 00:46

in the name of this cooperation model.

00:46 → 00:48

Dedicated meaning customized.

00:48 → 00:51

Team members are selected in accordance with the specific

00:51 → 00:53

needs of your project.

00:53 → 00:54

Product.

00:54 → 00:56

From the process of composing the team

00:57 → 01:00

our core focus remains the same, your product.

01:00 → 01:01

Team.

01:01 → 01:03

In a dedicated team model,

01:03 → 01:06

you get access to a range of qualified professionals who

01:06 → 01:08

operate like a remote department.

01:08 → 01:11

So instead of months spent on recruiting the right people and

01:11 → 01:13

integrating integrating them into your structures,

01:13 → 01:16

you can have your specialists set up and ready within a few weeks.

01:16 → 01:19

The typical self managed dedicated team consists of a

01:19 → 01:23

project manager, UX and UI designers, software developers,

01:23 → 01:26

quality assurance specialists and DevOps engineers.

01:26 → 01:30

The key to success is to find the right mix of skills that

01:30 → 01:33

add value to your product and eventually bring it to life.

01:33 → 01:36

The final lineup of your dedicated team depends on a few

01:36 → 01:38

factors like the maturity of your product,

01:38 → 01:42

the chosen tech and the people you already have on your side.

01:42 → 01:45

This is why the very first step in the process of setting up a

01:45 → 01:49

dedicated team is discussing and understanding project requirements.

01:49 → 01:52

A recommended and most thorough way to spell them out is a

01:52 → 01:55

product discovery workshop or a scoping session.

01:55 → 01:58

After that, we're ready to bring the best experts to the table.

01:58 → 02:00

Once the team is composed and approved,

02:00 → 02:02

we may start the show.

02:02 → 02:05

And it begins long before the first line of code in the heads

02:05 → 02:06

of our UX designers.

02:06 → 02:09

The whole solution has to be thought through in terms of

02:09 → 02:12

architecture and the logic in order to deliver the best

02:12 → 02:14

experience to your users.

02:14 → 02:17

The main outputs of this process are mock ups.

02:17 → 02:20

Our UI designers use them to create the first views in

02:20 → 02:22

Sketch and present them in InVision.

02:22 → 02:25

When we know how the app is supposed to work and look like,

02:25 → 02:28

we can move to the third stage, which is development.

02:28 → 02:31

The workflow consists of coding as well as testing.

02:32 → 02:34

The last step assumes the ongoing improvement in

02:34 → 02:39

experience optimization and continuous integration as well as delivery.

02:39 → 02:41

And how does it work in practice?

02:41 → 02:44

Let's picture it with the case study of a UK based startup,

02:44 → 02:45

Autium.

02:45 → 02:48

The founders were looking for support in building a software

02:48 → 02:51

as a service platform for vehicle fleet managers and drivers.

02:51 → 02:55

The goal was to create a simple yet functional MVP.

02:55 → 02:58

The founders didn't just need a high quality code base,

02:58 → 02:59

but most of all,

02:59 → 03:02

they wanted to work with team that understands their product.

03:02 → 03:04

We knew that to meet their expectations,

03:04 → 03:06

we had to start with a product design workshop.

03:06 → 03:09

This provided us with a great foundational base to compose a

03:09 → 03:12

well fitted self managed team consisting of an agile project

03:12 → 03:16

manager, two product designers, back end engineers,

03:16 → 03:17

front end and mobile engineers,

03:17 → 03:20

as well as a quality assurance specialist.

03:20 → 03:22

With such a cross functional team adjusted to the project

03:22 → 03:26

needs, it took us a couple of months to deliver the MVP.

03:26 → 03:28

But our work didn't stop there.

03:28 → 03:30

After releasing the first version of the app,

03:30 → 03:32

we focused on its further development.

03:32 → 03:36

To sum up, in a dedicated product team you get technical

03:36 → 03:38

consultation at the very beginning,

03:38 → 03:40

a self managed multidisciplinary team that

03:40 → 03:43

will offload your in house non tech employees.

03:43 → 03:46

UX and UI support from day zero.

03:46 → 03:50

A detailed quote and product roadmap at start.

03:50 → 03:52

Whether you're starting your business or upscaling your

03:52 → 03:55

product development, we're here to help.

03:55 → 03:57

Here at Merixstudio, we consider ourselves one big

03:57 → 04:00

team, not just a number of units.

04:00 → 04:01

So when we join your project,

04:01 → 04:04

we're on the same page from day one.