What's the first question that pops into your head when you hear something about Malty's adoption? That's right... steps to do it and time-consuming. Here we'll be going to guide you through some steps in order to make Malty your favourite system.
Adoption steps?
Yes! We sure have those here.
Following Malty's guidelines, we can give you a few tips & tricks about the adoption steps.
All projects, even the ones where the teams work horizontally, have some chain when deciding what to develop or adopt next. Here it's the same!
First, the product owner needs to be onboarded into the adoption process in order to estimate together with the designers and the developers which tasks are going to be onboarded during a specific period of time. This timestamp can be for one sprint, a quarter or the whole year.
Secondly, the designers are the next ones to step in and adopt Malty's components into the product designs in order to pass them to the development team.
The designers can see the design starter kit that we provide at the end of this page.
Last, but not least, the developers step in, and accordingly to the guidelines provided by the Designers and the timelines agreed with the product owners, start the development process into the adoption of Malty. This process can be by collaborating with Malty's internal team or by just building the features planned in the product using Malty's components.
The developers can see the development starter kit that we provide next.