1software Development Projectexampledr Vita Akstinaite2background A ✓ Solved

1 Software development project EXAMPLE Dr. Vita Akstinaite 2 Background & Assumptions â–ª Describe your Project Background here â–ª List your project Assumptions 3 (VA: in the next few slides please explain your project approach; the one in the example does not necessarily means that it works for your project!) Overall Project Approach 4 INITIATION ANALYSIS & DESIGN LAUNCH / RELEASE SUPPORTDELIVERY CLOSE Example of a Project Approach 5INITIATION Project Board • Simon Peters (Director) • TBC (Company/Client) • TBC (client) • TBC (service provider) Technical • Technical Lead • Lead/Senior Developer(s) • Developer(s) • Consultant(s) • Tester(s)/QA(s) Adoption and change • BA Oversight • Vita Akstinaite (Delivery) • TBC (Technical) Project Management Additional resource • BA • Architect • Designer • Infrastructure • Testing Lead • Support 6ANALYSIS & DESIGN â–ª Explain your requirements here: â–ª Functional requirements (i.e., hardware, software) â–ª Non-functional requirements (i.e., user experience) â–ª Visual design (i.e., how the app is going to look like?) 7 Deliverables (Example) Stage/Schedule Deliverable Acceptance criteria Test, Deploy & Extended Support Services Systems Manual The systems manual is a comprehensive document that describes in detail the information and activities required to ensure the system can be supported and managed on an ongoing basis.

The systems manual must include: 1. inventory of system components 2. installation instructions 3. configuration documentation 4. interface and batch jobs 5. release notes 6. backup and disaster recovery plan Summarise here what are you going to deliver? The app itself, probably some support for the app too? What about Help Desk? Additional services? 8DELIVERY â–ª Iterations â–ª Product backlog â–ª Reviews â–ª Testing Analysis Design ImplementationTesting Requirements Deployment Planning 9 Proposed timeline â–ª Example of how your plan could look like – change to what works for your plan and list all your activities Month May’19 Jun’19 Jul’19 Aug’19 Sep’19 Oct’19 Nov’19 Initiation Analysis and Design Iterative development UAT Infrastructure Migration Training Support (TBA) Discover Deploy Strategy Kick-off Reviews Go live sign-off Deliver: Development Iteration Cycles Test MigratePrepare Basic Advanced Set Up 10 Billing Activity Cost / Billing milestone Initiation 0,000 (to be split accordingly) Discovery and Design Development iterations Testing (UAT) Training Support Enhancements Activity Cost / Billing milestone Project kick off (payment upfront) 25 % Deploying to UAT/Production 50 % Project Closure 25 % Explain here how you are going to charge your client, when and what sums 11 Monitor: Project Status Jun July Aug Status 12.

19. 26. 02. 09. 16.

23. 02. 09. 16. 23.

30. • Finalise documentation • Acute flags (LTC) – confirm/customise • Testing Activity • Build GP data load process for EMIS • Receive pseudonomysed EMIS data • Hammersmith data • Key events Go live Kick-off Weekly meetings Milestones Achieved Responsibility Laura • Develop LTC/QoF process (SystemOne) Matt 26..02 Matt Matt • EMIS/System One integration TBC • Build referrals data • Build A&E data feed • Build Social Care data feed • Costing for Primary Care & Social Care • Amending costing algorithms for MH, CIDS, SUS data feeds Matt • Reporting tables TBC TBC TBC TBC TBC Simon Simon • Adding security layers for Tableau views TBC TBC • Environments set up (TBC) TBC 30.03 .20.03 • Deploy + Data load at SECSU Laura TBC Ready to go/ In progress At Risk On hold Deploy TBC UAT TBC • Population segmentation Matt 20.02 • Load received System One data TBC TBC TBC 04..02 • Build incremental load process for SystmOne TBC TBC TBC TBC 06.

13. 20. 27. Sep 24.02 • Showing Dr Tahir’s data TBC TBC TBC TBC UAT DeployGo live Explain how you are monitoring the progress visually! 12 Commercial control FINANCIALS Budget Actuals To Date Forecasts Commercial Basis Fixed price.

Budget at Complete $k Actual Cost $k Percent Complete Estimate To Complete $k Estimate At Complete $k Budget Variance $k Forecast Finish Date 300.00 20.0 7% 280.00 300.00 0.00 15/11/19 Explain how you are you tracking your costs. 13LAUNCH / RELEASE â–ª Explain how you are going to Launch your app? Will you provide any training or post-launch support? 14SUPPORT â–ª Do you support go-live and post go-live issues? â–ª Hosting environments? â–ª Support – 1st, 2nd, 3rd line? â–ª Operational improvements â–ª Additions to the app 15CLOSE What will be the process of closing your project? â–ª Client sign off â–ª Handover to support (if agreed) â–ª Final reports, closure in systems â–ª Final invoicing / Finance team 16 Ensuring project success List here your project success factors.

What will make this project work? For example: â–ª Ensuring involvement and alignment from all stakeholders â–ª Timely feedback â–ª Relevant workshops / meetings / reviews â–ª Monitoring risks â–ª Process for dealing with change 17 Anything else you want to add about your project â–ª ☺ Assignment 2: Project Plan (50%) This assignment is designed to demonstrate your understanding and application of core project management concepts and provide evidence of project management skills developed throughout this unit. Description: You are a Project Manager at IT Development Company. You have been assigned to deliver a project that is worth 0,000 fixed price over 6 months. It is a software development project – your team is supposed to develop a new version of “Murdoch Student LMS App†.

The requirements are all understood and signed off. Your task is to present an approach to starting the project up, proposed project timeline, how you would monitor/control the project, how you would manage stakeholders and your approach to commercial control. Keep it high level, aiming the presentation at management rather than technical. Your presentation should clearly define the following: • The project’s objectives; • The scope of work to be completed within this timeline; • Proposed plan for the delivery; • Billing schedule; • Key milestones (these could be aligned with the billing schedule); • Examples of risk and issue logs; • Your approach to reporting and stakeholder management. All the above-mentioned points should be presented in PowerPoint . Marking emphasis of this assignment will be on critical evaluation and demonstration of an understanding of the principles in project management.

Paper for above instructions

1. Project Background

The Murdoch Student Learning Management System (LMS) app is a crucial software tool aimed at enhancing the resources and delivery capabilities for students at Murdoch University. The existing version has provided valuable functionalities; however, the institution has identified certain gaps that need to be addressed. The objective of this project is to develop a new version of the Murdoch Student LMS app that improves user experience, integrates additional features, and aligns better with the needs of both students and faculty.
This project is valued at 0,000 and is aimed to be delivered over six months. The project assumptions are that all stakeholders are aligned; funding is secured; and that necessary personnel (developers, testers, project manager) are available throughout the project duration.

2. Project Assumptions

1. Stakeholder requirements are well-understood and documented.
2. Development and acceptance criteria for the project are clear and agreed upon by stakeholders.
3. Necessary resources (human and technological) will be available throughout the project.
4. All dependencies related to external systems will be managed effectively.
5. Risks are identified, and mitigation strategies are in place.
6. Regular communication will be maintained with all stakeholders for updates and feedback.
7. Changes in project scope will be managed through a formal change request process.
8. The development team is proficient in Agile methodologies for iterative development.
9. All software policies, compliance, and security measures will be adhered to during the development.
10. End-users will provide essential feedback during user acceptance testing (UAT).

3. Overall Project Approach

3.1 Initiation

The initiation phase will involve setting up the Project Board that consists of key stakeholders and technical leads. The roles I proposed for the project include:
- Project Director: Simon Peters
- Technical Lead: To be confirmed (TBC)
- Business Analysts: Vita Akstinaite (Delivery), TBC (Technical)
- Development Team: Senior developers, junior developers, QA testers, and other roles as necessary.

3.2 Analysis & Design

Requirements will be divided into functional and non-functional categories. Functional requirements may include:
- User authentication features.
- Course management functionality.
- Integration with external resources (e.g., library systems).
Non-functional requirements may encompass:
- Performance expectations (response time).
- User experience standards (ease of navigation).
- Security requirements (data protection).

3.3 Delivery

The project will follow an iterative Agile approach. The development will be broken down into several sprints, each ranging from two to four weeks. During each sprint, the teams will work on tasks from a prioritized product backlog, with regular reviews and testing to ensure alignment with project goals.

3.4 Launch/Release

Post development, user acceptance testing (UAT) will be conducted with selected end-users. Feedback from UAT will be incorporated as necessary. Training sessions will be provided to users to ensure they are comfortable with the new functionalities introduced in the LMS app.

3.5 Support

Ongoing support will be handled through multiple tiers:
- 1st line support: Help desk for immediate user queries.
- 2nd line support: Technical team handling more complex issues.
- 3rd line support: Involves developers for critical bugs or updates.

4. Proposed Timeline

| Month | Activity |
|----------------|---------------------------------------|
| Month 1 | Initiation and Analysis |
| Month 2 | Finalizing Requirements & Design |
| Month 3-4 | Iterative Development (Sprints 1-2) |
| Month 5 | User Acceptance Testing (UAT) |
| Month 6 | Launch & Post-Launch Support |

5. Billing Schedule

| Stage | Cost | Milestone |
|----------------------------|----------|-------------------------------|
| Project Kick-off | 5,000 | Upfront payment |
| End of Analysis & Design | 5,000 | After design approval |
| Deployment to UAT | 0,000 | After UAT completion |

6. Key Milestones

1. Completion of Requirements Gathering: Sign-off from stakeholders on the finalized requirements.
2. Design Approval: Deliver design mock-ups for stakeholder approval.
3. End of Each Sprint: Regular demos to stakeholders after each sprint for feedback.
4. UAT Completion: Sign-off on UAT results.
5. Project Closure: Sign-off from stakeholders and final invoicing.

7. Risk and Issue Logs

Risk Log Example

| ID | Description | Likelihood | Impact | Mitigation |
|------|---------------------------------|------------|--------|------------------------------------------------|
| R1 | Delay in Resource Allocation | Medium | High | Early identification of required resources |
| R2 | Changing Requirements | High | High | Establish a clear change control process |
| R3 | Technical Debt in Legacy Code | Medium | Medium | Regular coding reviews & follow best practices |

Issues Log Example

| ID | Description | Status | Owner | Resolution |
|------|---------------------------------|------------|--------|----------------------------------------|
| I1 | Delays in Testing | Open | Matt | Additional resources may be required |
| I2 | Integration Issues with APIs | In Progress | Laura | Engaging with API providers for support|

8. Reporting and Stakeholder Management

Regular status reports will be circulated bi-weekly to all stakeholders, summarizing the following:
- Progress against the project timeline.
- Financial status and any variances.
- Risk and issue status.
- Upcoming milestones and deliverables.
Stakeholder management will include:
- Weekly status meetings with key stakeholders to ensure alignment.
- User involvement in testing phases to enhance buy-in and user satisfaction.
- Adaptive communication strategies depending on stakeholder preferences.

Conclusion

Successful project management for the Murdoch Student LMS App involves a thorough understanding of project goals, stakeholder engagement, and adherence to Agile methodologies. By establishing clear objectives, following a structured approach, and maintaining open communication, the project aims to deliver a high-quality software product that meets the needs of its users.

References

1. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Control (12th ed.). Wiley.
2. PMBOK Guide (2017). The Project Management Institute.
3. Scrum Alliance. (2021). The Scrum Guide.
4. Highsmith, J. (2013). Agile Project Management: Creating Innovative Products (2nd ed.). Addison-Wesley.
5. Cohn, M. (2005). User Stories Applied: For Agile Software Development. Addison-Wesley.
6. Leach, L. P. (2014). Critical Chain Project Management. Artech House.
7. Schwalbe, K. (2019). Information Technology Project Management (8th ed.). Cengage Learning.
8. Meriam-Webster. (2023). "Stakeholder." Retrieved from https://www.merriam-webster.com/dictionary/stakeholder
9. D. Wysocki, R. (2010). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
10. ISO 21500:2021, Guidance on project management. International Organization for Standardization.
This project plan leverages foundational principles in project management while allowing for flexibility and responsiveness to stakeholder needs.