This document provides tips for building better agile development processes. It recommends starting improvements by focusing on results, communication, and feedback. Results include working software that is deployed and tested iteratively. Good communication involves talking to various project stakeholders. Feedback comes from code reviews, pair programming, and automatic testing. Processes like planning visibility, stand-ups, and retrospectives help ensure transparency. Overall, the document advocates adopting both technical and process best practices to fully realize the benefits of agile development.