Doing more… but not too much
Problem analysis, conversations, agreements, calls, code design, daily stand-ups, testing and implementation, pair programming, refactoring, meetings, code review, comments and defects and changes of the code, documentation and… much, much more. The bigger project, the more things have to be done, the more things are required to be done. But how much is too much? How to do enough instead of doing too much?
Spotkania, na których chcesz być obecny
“More meetings mean less time for work”. Is it true? Sometimes yes. When? In situations when you don’t see any progress after a meeting. When you are bored or exhausted after it. When a meeting was only about talking and not about moving forward. This talk will help you to change this. To turn valueless talks into productive discussions.