Lessons Learned from completing the Disabled on the Move project allowed all teams to express the hiccups found in the system during testing, issues and risks that will carried forth into production, suggestions on what needs improvement and what was actually learned during this entire project.
Disabled on the Move and its team were able to identify several lessons learned during the meeting and each were categorized as to if it held a specific date within the project window time or if it was throughout the entire project down to build or design. One of the items that were on the lessons learned which was identified on 6/2/14 was that the scope of the project was unclear at times. There were multiple changes made to requirements that were not reflected in the SRS, as a result there was a lot of time spent on rework to ensure that the requirements were all met. There was a debate about formal document process and who would take charge of making sure everything was documented. No standard process of how to write requirements and how the system should work (this impacted UAT testing). For future project requirements need to be assigned responsibilities to team members with the right historical knowledge and skillset. For those key players that have role changes in the middle of the project need to be transitioned properly off of the project in the event there are challenges so that the project can continue on. Constraints on time, people and money affected the ability to deliver on the project that included all of the functional requirements. Resource challenges made it difficult to move from an unreceptive approach to a more planed approach. Large-scale competing priorities stretched resources very tinny that in some cases there was not been enough time to devote to planning. Any important decisions were made but not communicated to the entire project team and often times it did not include all essential stakeholders. Inviting all testing teams (SIT/UAT) to...