Software Engineering, Project Management, and Effectiveness
“Agile Results” is the name of the “personal results system” inside Getting Results the Agile Way. People that have tried every personal productivity system under the sun tend to ask me, what’s so different about this system or why does it work? Here are the key things I usually say:
While it might seem new, and some concepts are, it’s really a system that I’ve been evolving over more than 10 years. I’ve used it to help people at Microsoft get faster, simpler, better results, and it’s how I’ve quickly ramped up folks on my project teams (you can read some of the testimonials and case studies.) I do recommend reading A Word from the Author -- It’s short, but it gives you some of the back-story on how the system evolved.
30 Days of Getting Results is an excellent introduction to the system in byte-sized posts:
Day 1 starts here:
Day 1 – Take a Tour of Getting Results the Agile Way
The series is loaded with inspiration. My favorite is:
Day 27 – Do Something Great
Looking forward to the book!
@ Jimmy -- Thank you. The book will finally be available in print shortly.
Completely agree with Jimmy ... Revisited Chapter 5 ("Monday Vision, Daily Outcomes, and Friday Reflection") yesterday and rediscovered a number of themes that continue to resonate. This is a terrific system. Thanks for assembling it J.D.!
@ Todd -- Thank you. I think the most important thing I did is pin it to a week and make it story-driven. We're wired for stories (there's a book on how we do scenario-planning even as babies) and using a week as the backdrop makes it easy to remember, practice, and improve -- with immediate results.