Lubo Drobny

Would you like to start with Scrum in your team? These are few hints from my experience how to make this process smooth, iterative & incremental: get commitment from the management & team define reason: why would you like to do Scrum? what problems it should solve for you? start with simple Kanban in one team: it is easier, you just need to manage 3 lists: backlog (todo), work in progress and done  focus on right priorities of backlog - person who defines the priorities will be 'product owner' setup quick way how to track work in progress and indicate 'impediments' -> daily stand-up; max 15 minutes meeting every day - moderator of the meeting will be 'scrum master', he will be also responsible for solving the 'impediments' focus on dependencies between the tasks to avoid 'impediments' start to put 'discoveries' into the backlog to pre-analyze tasks; discoveries should be done by architect or analyst what is the busi

When I was developing my practice project for high-school graduation exam I did a mistake 15 minutes before end of dedicated time. I somehow deleted my source code. It was horrible and I knew that I did not have any time to rewrite it from a scratch. Fortunately I realized that my source code editor was automatically doing backups and that saved me. I was lucky that time and I learnt my lesson that software factory cannot be chaos but it should be CHAOS: C ontinues  H elpful  A utomated  O rganized and  S mart. And I can tell that after 21 years I use more sophisticated software factory in my team which follows that principle: IDE for development:  allows fast writing/debugging/profiling of the code, documentation and configuration; the project setup must be generic so developers should be able to use any IDE without project setup change: Eclipse Source code repository:  provides effective & safe storing of the code, documentation and configuration with easy branching