The Qandidate blog has a new post today that "pulls back the curtain" as to how they manage their development process and get their work done.
At Qandidate.com we tried a lot of different project management tools and techniques. After two years of experimenting I want to share our current process, seen from my role as product owner (PO). One reason for sharing this, is to help you improve your process, but the most important reason is to start a discussion with you based on your experience, to improve our process even more. Our main rule at Qandidate.com is to embrace change. Always be open for changes that may or may not improve your process. If a change improves the process it's a win. If you didn't try it you will never know!
They walk through the three main points over the overall flow of work there:
- The process itself including two week sprints containing (unestimated) stories
- A demo and stakeholders meeting showing the work they've done during the sprint and get feedback from the stakeholders
- The stories and how they're created and when/how new ones are added (their "piano meetings").
They also include testing, both frontend and backend, and focus on small chunks of functionality instead of quick and dirty hacks. While their process won't work for every group (and is more of a "scrum-but..." setup) it is interesting to see how another group does their work.