Discipline and Agile

Working agile means you need to be more disciplined, not less! Think it’s one of the main reasons why is it so difficult to implement Scrum in a team (not speaking about whole organization). Here are several aspects: Estimation and planning Iteration planning with clients Daily follow-up with a whole team Iterative reviews of results and […]

Value structure

Forget old company structure – it doesn’t support growth! By the way did you notice that clients, customers or users are never represented in organizational structure? It is like company exists for itself, but not for the clients… Inspired by Niels Pflaeging ideas was writing some posts about what type of change we are introducing in my company. […]

Org. design: value structure

Was making presentation at http://agiledayriga.lv/ and after discussions with other speakers completely understood that we are on the right track. Here is my previous post that shares some problems from this theme. Brief description: It’s very easy to become hierarchical and turn into a “bank” when software company is growing fast. Is there a way to avoid that? […]

Organizational design – problems

I want to share my view on what problems are created by functional departments and hierarchical structure. Only organizing your company around value can solve these problems. But for that you need to have a bit different view on things and another level of transparency. Every team must know how they “earn money” (in quotes […]

Conclusion: When and Why to Fire a Scrum Master?

I was covering “Process and Responsibility” topics in my last post. To finish my analogy with Football Coach i want to suggest three main aspects that will help you to distinguish great Scrum Master from mediocre one. 1. Process is more important than value Process is only a tool that can help to achieve results. […]