Introduction
Working on new systems is a good move for companies, as it is sufficient for long-term improvement. The role of the project management is to make the team, develop a suitable procedure, and come up with a strategy, which makes the project successful. This project revolves around the process of developing secure web applications to enable the system integration in the company. A law firm wishes to implement a protected web application to use in its head office and other offices. The present solution is not integrated, so email is used to send information between offices. The firm also has an accounting system, which runs on a server at the head office. Customization is required to obtain expected outcomes of the project team. Central aspects of this study project methodology explanation (Agile) along with justification, list of 20 tasks, primary resources of the project, risk & strategies, well designed Gantt chart, showing the project’s tasks and the dependencies between them, a strategy to ensure impact, employee acceptance, training, and support. All procedures in this project are integrated with the project goals and objectives, which provides the rationale for success.
Project Methodology (Agile)
The company is looking to develop a secure web application to improve the internal process and contain the efficiency. The intentions are the production of correspondence, capturing client details, recording of histories, timesheet entries, client billing, and so on. To meet the goals, this is necessary to choose a project method, which can help the management to come up the high-quality outputs according to the expectations. The Agile project method has been selected for this particular project. Agile method is all about developing the short life cycles in the development process, which enable several milestones for the project management. Rapid and accurate project status is the significant advantage of the project management, as with each step, the team can evaluate the status of the project and make appropriate decisions.
Additional benefits of agile methodology in this project as under
- The project management can improve the productivity and quality, as frequent examination of process brings quality and integrity
- The management can meet the requirements of the customers in this method prominently, which leads towards the customer satisfaction.
- Due to transparency and spring meetings, the management can have a good project control
- Chances of failure can be removed through agile methodology in this project
- Agile method creates manager’s ability to judge the customer reaction and make decision quickly
· Justification
The selection of this project method can be justified due to complexities the web process. The secure web application is a complicated task for the project management, and development in different phases seems worthy. In each phase, the management will use different techniques to identify the issues and make the improvements accordingly. The significant advantage of the agile method in this project is the flexibility, which is needed in each phase. The project management can improvise in several phases and intend to improve the process to come up with quality and differentiated outputs. Thus, agile methodology is linked to the quality, and therefore, it is justified. The aim is the efficient project of the web development lifecycle, and the management can make the life cycle short, which also decrease the cost. Moreover, the work seems stable in this methodology, and this is also a big reason for this selection.
Now, in the next section, a list of prominent tasks in this project is depicting a relevant order, integrated with the agile project method.
· List of 20 Project Tasks
Initiation
- Evaluation & Recommendations
- Deliverable: Submit Project Charter
- Project Charter Signed/Approved
Planning
- Create Preliminary Scope Statement
- Determine Project Team
- Develop Project Plan
- Milestone: Project Plan Approval
Execution
- Project Kickoff Meeting
- Design System
- Install Development System
- Testing Phase
- Install Live System
- User Training
- Go Live
Control
- Project Management
- Risk Management
- Update Project Management Plan
Closet
- Audit Procurement
- Update Files/Records
- Gain Formal Acceptance
Main Resources of the Project
| Project Task | Resources |
| Evaluation Recommendations | Project Manager, Senior Software Developer |
| Deliverable: present Project agreement | Development Manager |
| Signing Charter | Office Staff, Programmer |
| Create ground work span declaration | Project Manager, Senior Software Developer, System Engineer |
| Making project Team | Programmer, Support Staff |
| Build up Project Plan | Senior Software Developer, Software Developer, Support Staff |
| Milestone: Project Plan endorsement | Programmer |
| Project beginning Meeting | Office Staff, Project Manager, Software Developer |
| Plan scheme | Development Manager |
| Install Development System | Junior Software Developer, Project Manager |
| Testing stage | Development Manager, Senior Software Developer |
| Install Live structure | Office Staff, Project Manager |
| User preparation | Programmer, Project Manager |
| Go Live | Development Manager, Programmer |
| Project administration | Senior Software Developer, Support Staff |
| Peril Management | Junior Software Developer, Office Staff |
| Update Project Management | Programmer, Software Developer |
| Inspection Procurement | Office Staff, Programmer, Project Manager |
| Inform Files/Records | Designer, Development Manager, System Engineer |
| Gain official Acceptance | Senior Software Developer, Software Developer, Support Staff |
Team structure diagram
Main risks in the project & Explanation
There are many risks in developing the secure web application to improve the system in the company. In his software project, different types of risks are schedule risk, programmatic risks, technical risks, operational risks, and operational risks. These risks are visible in the process, and the primary consideration of the management is to mitigate these risks in an efficient and lucrative manner. Following is a table, illustrating the different risk and the explanation of mitigation or elimination.
Scheduling & Feasibility
The project management along with the software developers in the project process can estimate the time for the project completion. However, due to the complexities of the project, there can be a delay in the project, which may also increase the cost and time. Apparently, the management has to pay extra for the developers and engineer on working more on the project. It is a significant risk of the project management, and it is the primary consideration of the project management.
Requirement Change
The change in the requirement is also in the limelight, as it is the project risk, especially in the software or web development process. In this particular project, the departments can intervene and ask for the change in the process to include the new trends in the integration. It is a waste of time and can hit the project sustainable.
Specification of Breakdown
Technically, when developing the secure web application to have integrated systems, there can be a significant conflict in coding and requirements. It is a significant risk that the specifications may contradict with the coding process, and it may waste immense time system engineer, developers, and the project management. Ultimately, the cost and time of the project may increase.
Programming Risk
Possibly, to meet the target, the project team may intend to get into the next step to save the time and cost. Due to this invention, there is a change of impaired programming. The project manager can face different errors in programming, and ultimately, they have to rework. It is a prominent risk that every software project may face the complicated situation.
Troubleshooting
Due to impairment of the systems in the project, troubleshooting is a significant risk. The systems, on which the management or development team has to work, may down, as it hits the project sustainability and delay. During the development process, the development team has to repeat the coding.
Ritual risks
The significant project risk is the disruption in the responsibilities of the project team. In day to day operation of the project, it is a significant risk that the management may fail to make a better implementation plan and execute accordingly. Disruption in the implementation process is a significant threat to the project management, and it can stop the process.
Gold Plating
In this specific project, there is always a chance of gold plating, as developers or programmers, intentionally, intend to add extra features to the project. Immense creativity in the process is harmful which may lead towards to the specifications and deliverables.
Production Impairment
Sometimes, in the project management, due to a long timeline, the team can take too much time to complete the process or task. In the end, the risk of overwork or burden in the production may increase, and it can also hit the process.
Design Compromise
According to expectation, it is necessary for the project management to meet the design requirement. Another risk that emerges in the process is the compromise on the design of the secure web application. It is due to other improvisations by the developers.
Financial Risk
With the passage of the time, due to some modifications or amendments, the cost of the project may increase, and this is one of the top risks for the project management.
| Risks | Mitigation Strategy |
| Scheduling & Feasibility | To reduce this risk, this is necessary to make the schedule for each activity separately. A single timeline must be designed for the single action, which can help the project management reduce the visibility of this risk. Learning from the existing project deriving the insights regarding the timer management is also an appropriate strategy. |
| Requirement Change | The project manager must have to develop the requirement specific documents and forward to all key stakeholders. It can reduce the chance of change in requirement during the process. |
| Specification of Breakdown | To avoid the breakdown, the project management, supporting staff from different departments and developers must have to collaborate to make the specifications, which can lead towards the useful coding and relevant outcomes. |
| Programming Risk | Intensive monitoring by the system engineer and senior software developer is proper to reduce the programming error.This strategy enables the completion of each task accurately with perfect coding. |
| Troubleshooting | Maintenance of systems with the passage of the time by an engineer is an excellent strategy to avoid the troubleshooting and contain the project sustainable. |
| Ritual risks | The procedural risk in the project can be reduced through the proper implementation process for each phase of the project. In each phase, the management can design different steps of implementation, which ensures the completion of the procedures. It also justifies the adaptation of the Agile project methodology. |
| Gold Plating | The strategy to mitigate gold plating in this web development operation is to be specific and trait developers and programmers to stick to the designs. Again, prominent monitoring and evaluation of each step in this agile method are proper to avoid the gold plating. |
| Production Impairment | The best strategy to reduce the risk of production impairment is setting a realistic plan or schedule. The flexibility in the planning and scheduling increase the time to complete different tasks. |
| Design Compromise | The strategy is to make a promising design structure of the web application. The initial training the best trait to reduce or evade this risk |
| Department Intervention | To eliminate the department intervention during the development process, an integrated departmental contain, which depicts the collaborations in planning is vital. |
Gantt chart (Microsoft Project)
Strategy to ensure the Impact
The new secure web application is valid for all employees working in different departments. Apparently, there is a need for an appropriate strategy to attract the impacted end user to accept the new applications and create an integrated system, which has never been experienced the company. Instead of sending emails for each document, the impacted end user will have to save the time and cost. Possibly, project management intends to come up with an adaptation strategy for the employees.
· Keeping Web Application or System on Radar
The best strategy for project management to make the employee accept the new technology is keeping this new output in the limelight or on the radar. It means that the management must have to remind the employees in different departments. Interestingly, it seems to target the customers in the market. However, in this case, the market segments are different organizational departments, and the customers are employees. A newly developed web application to have an integrated system is a brand for the project management
To boost the adaptation in the company by employees, the project management has to initiate the poster campaign in several departments. The poster campaign contains the success stories regarding the use of the software along with some key benefit. Interestingly, this initiative can also demonstrate the comparison of old systems and new methods, which can make the minds of employees to get rid of the old systems
The employees can accept the new applications through a comprehensive brief about the features. These are the real campaigns in departments by the developers and the project management to attract employees. Interestingly, this is to prove that the new system is efficient and easy to navigate as compared to the old one. There is a change of employee resistance, and they may contain the fear of the unknown. It is an exceptional strategy to decrease the employee resistance. These campaigns are kind of training process for employees, which can help them develop their skills and contain awareness to embrace the new application in information technology, production, accounting, sales, and supply chain departments.
This strategy is triggered by campaigns, which also include tips for the employee on a daily basis. After the installation, the system in departments, pop-ups on an hourly basis will assist employees to learn new things day by day and express expertise in operations.
Now, to reduce the resistance and let employees accept the new technology, reward program can also be initiated in this strategy. For Instance, in a campaign, the rewards are also to be on the radar. For Instance, when promoting the system in departments, the management will derive the behavior of employees. The management will reward specific and aggressive employee in this operation, and it increases the possibility of broad acceptance.
Wall of frame program is also a part of this strategy. After installation of this web system in departments, the management intends to announce rewards or facilities for that employee who provides extensive feedback and incomplete the goals or tasks of the system rapidly. It not only motivates the employee to adopt the technology but also convinces the new ones to maintain their office by using the new system.
· Sufficient Training & Support
Along with the strategy for technology or application acceptance, the training for accounting, IT, production and another department, which are integrated with the system, is imperative. Sufficient training refers the necessary training to understand the complexities and main features of applications to initiate and sustain the process. The support from system engineer, developers, designers, and programmers is crucial in this training process to increase the skills of employees and let them be productive and efficient in operations. During and beyond go live, the support of professional or experts along with the project team are worthy to come up with expected results.
Acceptance criteria have to be made by the management to ensure the project success. For Instance, in this criterion, the project management has to contain task description and division of tasks among members who have to interact with employees. Coding and test cases are visible in this process. The central aspect of acceptance criteria is user stories, which can make the minds of employees. First, the user has to assess the needs of the new system, navigate the stories, and make a comparison to make a decision. An acceptance criterion is negotiable between the project owner and department teams.
Conclusion
In the end, this is to conclude that this project can change the procedures of the company, as integrated systems in all departments are working to improve the process and enable efficiently along with the contribution of all key stakeholders. In this particulate project, several project risks are described in the agile methodology with some practical strategies for elimination. There is a proper team, which has also been depicted in team diagram. Through comprehensive Gantt chart, tasks, durations, and resources are explained. Captivatingly, the management came up with a differentiated strategy for employees to accept new secure web applications. It is a remarkable project to enable the integrated ad automated system, which a can improve coordination and overall performances of the company for a long run.
References
Burdman, J. R., 1999. Collaborative Web Development: Strategies and Best Practices for Web Teams, Volume 1. s.l.:Addison-Wesley Professional.
Chemuturi, M. & Cagley, T. M., 2010. Mastering Software Project Management: Best Practices, Tools, and Techniques. s.l.:J. Ross Publishing.
Cobb, C. G., 2011. Making Sense of Agile Project Management: Balancing Control and Agility. s.l.:John Wiley & Sons.
Emond, J. & Steins, C., 2012 . Pro Web Project Management. s.l.:Apress.
Highsmith, J. A. & Highsmith, J., 2010 . Agile Project Management: Creating Innovative Products. s.l.:Addison-Wesley.
Lazar, J., 2001 . User-centered Web Development. s.l.:Jones & Bartlett Learning.
Luckey, T. & Phillips, J., 2011 . Software Project Management For Dummies. s.l.:John Wiley & Sons.
Sacks, M., 2012. Pro Website Development and Operations: Streamlining DevOps for large-scale websites. s.l.:Apress.
Stellman, A. & Greene, J., 2005 . Applied Software Project Management. s.l.:”O’Reilly Media, Inc.
+447462439809