Scrum excellence consists of breaking the resistance to Agile without fighting
Keep your feature enhancements close, and your defects closer.
To fix one hundred bugs with one hundred heroics is not the acme of skill. To subdue the code without manual testing is the acme of skill.
The developer will win who knows when to refactor and when to refactor again.
Let your object be frequent deployment, not lengthy death marches
Sprint invincibility lies in careful capacity planning; the possibility of victory in improved velocity.
To know your product, you must groom your backlog.
Plan Like Scrum Tzu!
Scrum without strategic vision is the slowest route to victory. Strategic vision without Scrum is the noise before a failed project.
There is no instance of a Scrum team having benefited from longer Sprints.
A Scrum Master leads by example, not by force.
If you know the code and have automated testing, you need not to fear the result of a hundred enhancements. If you have automated testing but don’t know the code, for every bug fixed you will also suffer another bug. If you don’t know the code and don’t have automated testing, you will succumb to every enhancement request.
Do you plan like Scrum Tzu?
Regard your developers as your children, and they will follow you into the deepest spaghetti code; look on them as your own beloved children, and they will stand by you even on a waterfall project.
Even the finest code, left untended without constant refactoring, will eventually die.
Be extremely small in a code change, even until most code is test code. Be extremely BDD, even to the point of over thinking. Thereby you can be the director of the application’s fate.
There are not more than five Jira issue types, yet the combinations of these five give rise to more products than can ever be downloaded.
Victory usually goes to the Scrum team who has a more available Product Owner.
In the midst of prioritization chaos, there is also opportunity
Always be planning
Know your strategic product goals and you will win all projects.
Be extremely BDD, even to the point of most code is test code. Be extremely MVP, even to the point of not enough. Thereby you can be the director of the product’s fate.
If the Scrum Master mind is willing, the daily scrum could go on and on solving too many things.
Opportunities multiply as code is minimized
Engage Scrum team members with the Scrum Ceremonies they expect; it is what they are able to discern and confirms their projections. It settles them into predictable patterns of successful execution, occupying their minds while you wait for the extraordinary moment — a velocity improvement idea.