Quality Assurance Functionality: 4 steps to open a table. It can be reduced to 2 steps. More clear user interface. There are some functions missing which can improve the user functionality such as a function that does not allow late clock-ins, a function that reroutes the printers, and a function that modifies an order.
System Outputs Some of the reports and fields have to be improved. Similarly, the screen output for users also needs to be improved.
Performance System’s Operating system and hardware were not capable to process the data properly. File server had a low memory to keep the sales transactions. Internet connection was slow for credit card processes.
Reliability There has been a loss of data written into the servers files. System had crashed a couple of times even if there was a single process. Under these conditions, system considered as “unreliable.”
Underlines from weekly reports Reports after Initiation 1-There has been some tasks finished earlier than as they planned. 2-Necessary Adjustment have been made to the Gantt charts
Reports after planning 1-In planning, we have some resource conflicts. It was solved by resource leveling. 2-Due to this problem, we fell behind the schedule but this did not cause a significant problem. 3-Projects Organizational conflict has been solved after this step. 4-Implementation outsourced to Ibertech Inc.
During the Execution 1-project team checked the system for quality purposes. 2-project team decided to hire an outside consultation after they checked the system. 3-Consulting firm found some screen output and functionality problems. 4-Consulting firm reported that hardware is incapable.
Change Control Time changes have been made after Initiation and planning. There will be a 20-days extension on the projects’ completion date due to the change on scope. This change has been fallowed by projects’ sub group.(Emergency Group) The Budged adjustments have been updated due to the solicitation costs.
Close Out 1-Procurement Close-Out Has not been accomplished because of the change in scope and the requirements that were not met by the contractor. Additional 20 days to close out the procurement.
Success 1- Every task was finished on time or very close as it was planned prior to executing. 2-It is always a good practice to think and leave financial backups for the possibility that you could not finish the project on time. 3-To see the fact that “No matter how good you are there is always something that you can miss.” 4- Project team was also coordinated well and had a little conflict on decisions.
Failure: The scope management was a failure of the project. There are 4 main reasons why the scope was expanded: 1- Project team had a lack of providing user input to Contractor. 2- Project team had a lack of defining the requirements and specifications. 3- Lack of expert knowledge. 4- Lack of resources (resource over allocation)
Lessons Learned Bad Practice to do 1- Do not go ahead the project unless you fully understand the user requirements 2- Work with one or more real users who will be actually using the system. 3- Do not underestimate expert knowledge, hire somebody or a company to provide expert knowledge.
Continued 4- Outsourced parts of the projects might have some quality exploits. Never outsource your Hardware installation or have a strict contract with contractor company. 5- Avoid over allocation of the resources.
Good Practice to Do 1- Have a good communication with stakeholders. Tell them what has been wrong and how you fix the problem. That is what happened when our CEO seemed uneasy about project’s success and how he was convinced when the project Manager made the necessary explanations. 2- Always leave some financial backup and keep it in secret. 3-Have a good contract solicitor. That’s how we saved the extra costs caused by contractor.
Continued 4- Always control what you are doing and what you have requested for change has taken effect. 5- Form a project subgroup to fallow unexpected scope and time changes. We call it emergency group.