How to ensure that requests from different sources become formalized and clear requirements, and address communication, clear interpretation, accountability and transparency.
Workflow for the Requirements in the Distributed team
How to ensure that requests from different sources become formalized and clear requirements, and address communication, clear interpretation, accountability and transparency.
Warning: don't misinterpret scrum for agile as a whole 🙂 Around a year ago I wrote a yearly retrospect on how the workflow at SkuVault is organized, and how we set up our jira boards to work in sprints. sprints and their goals There was no Kanban backlog at the moment, and we used Scrum … Continue reading Why we ditched Scrum in favor of Kanban in JIRA
In order for the distrubited teams to work, you got to have a clear flow, a set of general rules, that will fence the process and allow people to collaborate effectively around the globe. If everything is set up correctly, you are able to create amazing products with global professionals, and cover customer support 20+ … Continue reading Communication in distributed teams: Messenger & Rules
So it happened - I managed to gather 2 people for PM & BA meetup (without any PR xD). After visiting Vienna, I desperately wanted a platform to share knowledge or / and mock each other on PM & BA failures. So I created one:  Ufa Project Management & Business Analysis Group Initial meeting consisted of … Continue reading Project Management & Business Analysis Meetup – Ufa
Last year guys from SkuVault offered me an amazing opportunity to help the company manage a growing development team, create organized schedule, establish workflow that reflects the company goals . For those who don't know - SkuVault is a Warehouse Management System (WMS). Like a swiss army knife, SkuVault manages and syncs your inventory across … Continue reading Year Retrospective @ SkuVault
Recently my colleague, Tim, decided to try out Planning Poker, to have better estimations. Planning is essential, and scrum already offers a framework of how to deal with planning. But over the course of my work and experience with scrum techniques, team usually shapes Previous experience showed that daily scrum meetings are merely pointless. Direct communication / skype … Continue reading Tuning up Scrum Approach
It's all about the process I might be a captain obvious here, but supporting a process for an analyst / pm is a more important, than micromanaging tasks amongst developer pool. When a new team member steps in, who's responsibility is to manage development processes, she needs to find how to make business processes inside a … Continue reading Manage process, not people
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 … Continue reading Team Spirit + Exciting Project = Good Product (and vice versa)
When developing Storia.me iPhone app, we had the following circles to deliver to: Developers QA Early adopters General Audience (AppStore) And the following problems to solve: Provide Beta access with faster update pace and immediate critical bug fixing for early adopters (as in microsoft’s inner circle); Make AppStore version as stable as possible; Receive feedback … Continue reading Storia.me App Rollout: Better Feedback Loop, Faster Iterations
Well-coordinated work across teams - let's say design and development - is a huge deal when it comes to delivering a good product on time! So, part of my job as a project manager is making sure that the assets passed from design into development are ready for implementation. At the very heart of the … Continue reading Improving App Design Review, Ensuring Design is Ready for Development