Async Remote

Table of Contents Introduction Story of size 1 Forget about sprints Stream Of Work Chronos vs. Kairos Can developers be project managers? Developer's attitude Customers Meetings Developers creating tickets Specification as floating ticket Working with tickets Start from the middle Don't focus on providing the data What if you really need to use the real data? Technical decisions Defer Detecting actors early Starting from the middle is pivot-friendly When to stop working in the middle? Gradual migration of persistence Code is not a stone Outsourcing less important parts Optimise for the developer brain Summary Communication as tickets (Over-) Communication On async Why should you try to lean towards more async communication? When sync When async again Knowledge sharing Standups and meetings Async standups Tooling Friendly workflow environment Bonus: How to get anything done? - 4 tips Start enough times Accept negative feelings and start working Love the grind Detach yourself from results Now Bonus: Am I ignored in my async team? Typical Project Management smells Management thinks ``you can build perfect solution from day one with all Nice To Have, just add more developers'' Protips Yet another weekly meeting is scheduled The ``cheaper'' developer makes Research and Development tasks and the more expensive one fix his bugs. The project knowledge and tickets are distributed among different tools (Trello, Pivotal, EverNote). Bonus: Q&A Links The end Feedback