Dont forget the Retrospective.
Regardless of the meeting name or approach to doing so, one of the key tenets of Agile development is refining your approach and adapting to change. That means looking at what you did, thinking about how you can improve, and continually getting better.
Be agile, not Agile.
Being agile does not mean you have to follow exactly what another Scrum project did, or force yourself to use Kanban boards, or hold your team to official DSDM rules. Leverage the knowledge gained from prior work, but evolve to do what is best for yours.
Agile can and does work for BI in practice and may be more important for BI than for many other projects. Since users often dont really know what they want in BI projects, giving them the opportunity to constantly tack and adjust a projects evolutionary progress is vitally important to success. Here are six key approaches from CBIG Consulting Principal John Harmann that have served as starting points for many BI projects. Since the core principles of Agile involve adapting to change, stress the virtues of working closely with the customer and the team, and continually creating working software. And keep in mind that while adhering to rigid rules or dealing in absolutes definitely has merits in promoting consistent quality in many other aspects of work and industry, Agile in a BI environment functions best when it allows BI teams to advance client goals in a more flexible environment. Also see Insurers' 4 Most Promising Tech Initiatives This slideshow originally appeared at Information Management.