Agile Checklist Part 1
I will be adding notes an agile projects on an occasional basis for all considering how to go about initiating an agile software project.

Make sure you have the support of project and line management.

Often some developers are keen to go agile while others are reserved. You can't do it alone (unless your software requires no changed or new interfaces)! And unless you have the go ahead from management you will find them making requirements you cannot fulfill, e.g. you cannot declare an overall "code ready" at the time they will be expecting when you have several iterations including unit and integration testing.

It is also necessary to define in what sense your project is agile since there are various approaches and degrees to agile, and to ensure management has the same understanding. I often find there are misconceptions such as: agile allows for continuously changing requirements. Also note that agile requires a high degree of transparency. You may find that management does not feel easy about too much transparency within the project!