Sometimes Scrum is not the best fit project management approach. The usual reasons for this are:
Work cannot be properly planned in advance
The Scrum basic principles cannot be followed due to various objective reasons
There are too many incoming changes to deal with in the Sprint scope
Estimations are hard to be done correctly
In such situations, Kanban may be the most effective approach. Kanban is set to support continuous delivery with maximum flexibility. For Kanban we use the following best practices:
Tasks currently under development
Rasks marked as completed by the team
Tasks accepted by the client
We organize the project activities into four type of categories:
We have daily team meetings, similar with Scrum stand-up meetings, where team members report statuses and issues.
While Scrum drives productivity by limiting the work time available in a Sprint, Kanban drives productivity and velocity by limiting the number of active, concurrent issues. Time estimation is no longer part of the project management process.
We're hiring an experienced senior backend (ideally 5+ years) web-service engineer interested in creating optimized and scalable front-end solutions driving engaging web experiences through web and mobile. More specifically we are looking for a talented developer that, within a versatile Agile team, would take an active role in creating and evolving the backend source code, in our quick-delivery multi project environment.