Yeah I had to suffer through the full-blown training from a "Senior Agile Coach" like the author - taken extremely seriously by the management at the time, so I

Yeah I had to suffer through the full-blown training from a "Senior Agile Coach" like the author - taken extremely seriously by the management at the time, so I can see how a bunch of people who took this stuff literally - including the "coaches" - are a bit heartbroken now. My employer who ordered that expensive training collapsed several months after that. But, trying to distill all the formalistic nonsense into usable points, they actually do have a few. My personal takeaways: - try to ship faster (try daily for a webapp), but do what feels right for you - have some task board and scrub it regularly (once every week or two, whatever) - learn to use ballpark estimates (1 hour, 1 day, 1 week - or whatever else floats your boat. Fibonacci, none of this stuff will ever be realistic - just get the order of magnitude) - have short meetings about blockers, but schedule stuff for later the moment someone starts banging on for too long - yeah, and try to break stuff down into smaller, more manageable pieces, the spec, the PR's, pretty much everything No idea if this is "SCRUM" or not, but this has worked for me so far...