-
Notifications
You must be signed in to change notification settings - Fork 1
Project Parameters
Through meetings with the Product Owner and Product Sponsor, a clear scope of work has been determined for this project. Due to the experimental nature of some goals, it is expected that this scope may change over time, and these changes will be communicated between the team and the sponsor.
- A frontend interface that is usable by administrative staff to receive, view, and update submitted purchase reimbursement requests.
- A submittable form built in CHEFS.
- An API that manages incoming requests and interaction with the frontend and database components.
- Documentation that adequately explains the project and the technologies used within.
- Deployment workflows that handle the process of deploying the application into the OpenShift platform.
- Application design should meet the standards required by BC Government, including user- interface conventions, documentation expectations, and security requirements.
- Application is deployed to the OpenShift cloud hosted by BC Government.
- Application is secured with authentication using the existing Keycloak provider.
- Define and implement process for using data with business analytics tools, such as PowerBI.
The following constraints have been identified by the project team and its sponsors:
To meet the deadline of the Capstone Symposium event, application development should end at the start of August at the latest. The team is also expected to attend classes on Tuesday and Thursday, further reducing available working hours.
This project has only one member to participate in application development or completion of school assignments. As a result, the expected velocity of the project may be lower compared to other projects.
Because this project relies on additional services not maintained by the IMB, there is a limitation on the features offered by those services. Any features that this project identifies as needed but not yet implemented will likely not exist before the end of the project.
Some factors on the team’s and client’s availability, knowledge, and resources have been assumed during the planning of this project. They can be summarized below:
- The client assumes ownership of the code repository.
- Technical assistance and expert knowledge will be available to the team if needed during standard working hours.
- There is a general level of technical proficiency within the client organization’s staff.
- Team members have the necessary equipment to develop the application, which includes a computer and a means to participate in virtual meetings.
- The team is present at the office during days without classes for regular working hours.
- An environment for deployment of the project will be hosted at cost to the client.
- Workspaces at the organization’s location will be available for the team to use.
- Authorization services are maintained within the organization.
Documentation will be created in tandem with the application and will be available throughout the entirety of the project. This documentation remains in the GitHub repository and is accessible at any time, during or after the project. Sessions with potential users will be offered at the project’s completion to ensure they are familiar with its operation.
For the prospect of future development, the organization has complete access to the GitHub repository, the OpenShift environment, and any required application secrets. Development should be able to continue with minimal investment.
As the project has progressed, the risks that were initially outlined at the project's inception still hold true. However, the team has become more familiar with some of the elements described in these risks, resulting in lower priority ratings. This could be seen as a result of the mitigating strategy undertaken by the team which involved additional research and effort in becoming familiar with the risky elements.
| Risk | Description | Owner & Recommendation | Priority | Strategy |
|---|---|---|---|---|
| 1 | Reliance on Non-managed Services: Some services used in this project are managed by other groups within the provincial government. | Sponsor: Communicate with service managers in the event of downtime or feature issues. | Low | Accept |
| 2 | Unfamiliarity with Common Components: Common components, such as CHEFS and Keycloak, have little documentation on use and integration with web applications. | Team: Assess the components for potential issues and develop solutions where possible. | Medium | Mitigate |
| 3 | Lack of Experience with File Storage: The proposed project includes some form of file uploading. The team is not familiar with orchestrating file storage in an application or database. | Team: Research into possible solutions and reach out to specialists within the organization. | Medium | Mitigate |