Workflow for the Requirements in the Distributed team

Thu, 24 Aug 2017 00:00:00 +0000

This is basically the anatomy of a distributed team, working on requirements. Key point here is that this is the process working for us, in current configuration, and it’s effective.

Disclaimer: Every organization is different: from internal structure to how it communicates with the outer world. So no workflow is a silver bullet.

*Disclaimer 2: SkuVault is an ever-improving team of ~50 people, distributed across 10 timezones, 2 different versions, and serving loyal clients worldwide 24/7. Learn more about Communication in distributed teams: Messenger & Rules, or *Why we ditched Scrum, in favor of Kanban in JIRA

Team Spirit + Exciting Project = Good Product (and vice versa)

Tue, 16 Jun 2015 00:00:00 +0000

Product is crafted by people. It is not a sum of collaborative work. It’s usually a combination of work, excitement, collaborative ideas, feedback loop inside the team throughout the whole project lifecycle.

Passion is right at the heart of every person, and if environment tends to motivate - a person will work hard to achieve a good result (appreciated by the team and himself). Moreover, working with passionate team amplifies the overall product, makes it bigger than sum of efforts.

Development on Marat Kiniabulatov | Agile Coach, OKR, PMO

Workflow for the Requirements in the Distributed team

Team Spirit + Exciting Project = Good Product (and vice versa)