When we meet a new client, say, a startup in the automotive industry or a consumer electronics manufacturer, we quite often receive dozens of questions on how development workflow actually goes. In this article, we've covered the project management side — participants and their roles, basic concepts, project management software, as well as reasons of failures and ways to success.
There are two major ways to cooperate with a software or hardware development company: a dedicated team or a fixed-cost project. In this article we will explain when it’s more reasonable to go with a dedicated team model, how it might look, pros and cons, and how you can make this model more (and less) effective.
When you have already found the Team for your software or hardware product development and all the requirements are ready, you’re probably on the stage of planning the development process itself. We described in our previous article some general principles of the workflow (what a sprint and backlog mean, who stakeholders and product owner are).