Imagine your team has done everything that was required. They’re happy. At the same time the client is angry because the work is incomplete. Say “hi” to poor, assumed or undefined definition of done - source of many miserable failures.
Project estimates are extremely difficult and important. Clients need ones they can rely on. They put them on their roadmaps. They make promises to their stakeholders based on the estimates. They budget according to them. There's always a pressure for the estimates to be low (cheap), yet accurate. At the same time we never have enough information about the project. This is the crux of every project. That's the intersection of plans, expectations, priorities, assumptions and uncertainties. How do you handle all that?
Have you heard about Scrum, but…? This means “we do scrum, but…” we don’t do retrospectives, don’t do daily standups, etc. Well, there’s a deep wisdom behind all the Scrum practices we give up. Be aware of the risks you create and know how to counteract them. This is a first post in a series that aims to show how you can keep the benefits of Scrum in real life.
Building high performance apps tends to result in a lot of learning and plenty of interesting stories. That's why in the beginning of 2016 we've silently launched our new blog: tech.evojam.com. This is a hardcore, technological publication devoted to engineering of serious web applications. Ones that need to handle a lot of traffic or data.