Similar to the first question, all of this should be addressed in both your project vision and roadmap documentation. The second question that auditors might need from your agile project is how the project will add business value. Therefore, your agile projects need to measure against this objective, and it would be noted in your project documentation that this objective is not only considered, but how this agile project will contribute or meet that objective. If you are an e-commerce site, the business objective could be to increase revenue by 20%. In fact, no matter the methodology, any successful project requires quantifiable objectives from business which can be measured at the end of the project to ascertain the project’s success. Thus, there should be documentation that is produced at the start of any agile project where the business objectives and strategic alignment are noted and considered in the project. While agile methodologies do not stress high volumes of documentation, they do not advocate no documentation. Considering that any agile project begins with a vision and project roadmap, it should be evident that your project had to be considerate of the business strategic needs as an input to both the vision and product roadmap. Looking at the first item, the business needs to be able to assess that the agile project will align with the strategic objectives of your organization. It might require your organization to be open to modifying some of their traditional approaches to project management governance in order to accommodate your agile methodology. Simply looking at these questions, any agile project manager can derive approaches to satisfy these needs without compromising on agile principles. Is the project compliant with any regulatory requirements?.
0 Comments
Leave a Reply. |