Here a “light” Agile Software Development checklist that I have used for many years to introduce Agile in organization. I usually introduce few items per week.

Product Management

• A product Backlog, estimated and prioritized by a “Product Owner” is used
• A “Release Plan” exists and is known by the team
• A “Company Strategy” exists and is known by the team
• Features are divided into “User Stories”
• The “User Stories” are estimated by the whole team using “Planning Poker”

Workflow

• The development work is divided into iterations or timeboxed “Sprints” or “Iterations”
• A “kanban” or “Information Radiator” is used
• The tasks are not assigned, the team organizes itself
• The “Velocity” of the team is known
• No outsider can interfere directly with the team during an iteration
• “Daily Meetings” take place and do not last more than 10 minutes
• A “Sprint Review” is organized and the output recorded
• A demonstration is held at the end of each iteration
• The problems are tracked and by the “Scrum Master” and/or management
• A proper Retrospective is held
• A “Burndown” graph is updated daily
• The “Code Reviews” are systematically organized

Development Tools & Rules

• A source controller is in place
• A continuous integration build server is used and testing (unit & guidelines) takes place at each commit
• The packaging of the product is fully automated
• A (simple) bug management tool is used
• Each bug is reproduced in a single test and then corrected
• 80% of the code is covered by automated testing
• A “Solution Log” in WIKI form is used
• The “Coding Guidelines” are defined and understood by all
• A maximum of 40 work hours per week!

Please note that any numbers above can be adjusted to your reality.