CMGT/410: Bugs vs. Feature Requests
BlackWolf
PROJECTSCHEDULINGANDDOCUMENTATION.pptxPROJECT SCHEDULING AND DOCUMENTATION
NAME
INSTITUION
AFFILIATION
HIGH LEVEL DEFINITION
In project management, IT-related softwares are quite common.
For this particular project, the intention is to carefully design a banking software through which bank clients can undertake various activities.
As observed in the world today, most people have, in recent times, tended to more or less prefer as an aspect of convenience in all endeavours.
With the creation of such a digital platform, convenience will not only be the only advantage with the software, but also bank activities will become much more streamlined
. For the successful creation of the intended banking software, there may be a number of variables that may need to be considered which include; the security of the software, the integration of the network and software and functionality of the software(Scope Planning, (n.d.)).
2
BUSINESS CASE
The intended software that will be developed seeks to streamline banking services for many banking firms.
With various activities currently going digital, banking should as well be digitized. Streamlining banking, particularly for many customers, will hence increase the numbers of transactions conveniently.
By building a platform that easily allows for seamless transactions as well provides a secure platform within which customers can trust to handle their transactions (Scope Planning. (n.d.)).
The software hence is intended to authenticate users and protect their data as a way conveniently offer banking and other financial services to its users ("Scope Planning", (n.d.)).
3
PROJECT APPROACH
Agile methodology is most preferred as it rather flexible and hence allowing the project ought to be divided into phases that can be shared among various team members.
These phases will include:
The idea generation phase
the pre-feasibility phase
The feasibility phase
The development and execution phase
The commissioning phase
The launching phase
Post-implementation phase
The idea generation phase within which the ideas for the project will be tabled, describing the business need to be addressed (“Project planning in Agile methodology”, 2018)
The pre-feasibility phase which allows for the evaluation of any existing proposal while keen attention to financial, technical, and operational viability of the project (“Project planning in Agile methodology”, 2018).
The feasibility phase which ensures that the business need is addressed. Keen analysis can be conducted to determine any risks (“Project planning in Agile methodology”, 2018)
The development and execution phase, which involves; design, development, and the creation of the solution. Supporting manuals and other relevant documents are as well developed in this phase (“Project planning in Agile methodology”, 2018).
The commissioning phase which the software can be tested in an operational environment (“Project planning in Agile methodology”, 2018).
The launching phase which marks the beginning of the operation of the software (“Project planning in Agile methodology”, 2018).
The post-implementation phase where the software can be assessed on its functionality after a given duration of time (“Project planning in Agile methodology”, 2018).
4
DESCRIPTION OF TEAM MEMBERS AND ROLES
In project management, there are various roles played by different people to guarantee the success of the project
Each personnel involved has a different role to play to guarantee the success of the project. Some of the crucial team members include;
A project manager
Project stakeholder
Business analyst
Software developers
Project manager
. A project manager is the leader of the team involved in project development.
He or she hence provides support to the team by ensuring all necessary requirements needed in the project management are availed to facilitate the success of the project
Project stakeholder
A project stakeholder is the overall decision maker of all decisions relevant to the project. A stakeholder can then influence the success of the project by determining how resources will be allocated to the project
Business analyst
primarily supports a product owner by analyzing the business domain of the project, grooming, and stocking the product backlog.
A business analyst breaks down all aspects relevant to the business domain and describes the problem intended to be solved
Software developer
A software developer is primarily concerned with the programming and execution of software and deliver an outcome at the end
5
PROJECT SCOPE
The bank software intended to provide financial service to banks hence bringing about convenience in banking.
With the aim to improve and streamline banking services, this particular project will aim at leveraging the presently available technological infrastructure for a worthy course.
Most processes are currently going digital bringing about an aspect of convenience and ease of accessibility to banking firms and customers alike
The project will majorly revolutionize the interaction between bank customers and banking firms to provide better the urgently needed software ("Scope Planning", (n.d.)).
6
OUT OF SCOPE
The software is not limited to a given capacity on the number of people in which it can connect seamlessly at any particular.
The capacity that the software can hold is majorly dependent on the bank's server's capacity.
The banking is actively available to users provided they are connected to the internet.
The software will not be intended to be in operation on specific hours of the day or in certain locations.
Having a weak internet connection may compromise the usability of the software
The software is at any one time logged into a user's bank account to access the variety of services offered by the bank. Therefore, Various locations will have varied internet strengths hence finding a location with strong internet connectivity makes the usability of the software much more enjoyable and less straining (Kassaye, (n.d.)).
7
TIMELINE
It is expected that the development, implementation and execution will take roughly 1032 hours
Each phase has been allocated enough time for execution as follows;
Idea generation – 120 hours
Evaluation – 200 hours
Development and execution – 400 hours
Testing – 96 hours
Launching of the software – 96 hours
Post-implementation Functionality assessment – 120 hours
Idea generation
Proposal drafting – 48 hours
Concept generation – 48 hours
Initiation – 24 hours
Evaluation
Pre-feasibility evaluation – 100 hours
Feasibility evaluation – 100 hours
Development and execution
Designing – 72 hours
Coding and development – 280 hours
Drafting of manuals – 48 hours
Testing
Alpha testing – 48 hours
Beta testing - 48 hours
Launching of the software
Commissioning of the software application – 24 hours
Release of the software – 24 hours
Implementation -48 hours
Post-implementation Functionality assessment
Maintenance – 48 hours
Auditing – 72 hours
Business review – 48 hours
8
BUDGET AND BUDGET REPORTING
To guarantee the success of this project, a budget ought to be allocated
Below is the budgetary allocation of every phase:
Analysis and survey - $ 50,000
Development and implementation
In-house - $ 150,000
Outsourced – $ 20,000
Commissioning
Alpha test - $ 10,000
Beta test - $ 10,000
Launch - $ 50,000
Post-implementation
Software audit - $ 25,000
Business review - $ 10,000
RISKS, CAUTION AND DISCLAIMERS
The project aims to leverage and take advantage of new technology hence a new set of risk factors arise. These include;
Data Security and privacy
In banking, there are huge chunks of information being developed with every touch of a screen or click of a button. To best secure the information, it is important to develop measures to protect bank customers from cyber-crime. Data will then be encrypted to prevent easy deception of information either in storage or in transit
Authorization
Most of the data stored and generated in the software environment will majorly be in numerical form. Therefore, considering the sensitivity of the data, every step or process undertaken in the software will be authenticated.
Data security and privacy
Before logging in, it will be important to verify the user by the various available means such as pins, passwords or biometrics. There will be then a well-recorded history log to store activities such as transactions, loggings and other aspects taking place in the software. Notifications of access and malicious activity can be enabled for informative purposes to the bank as well as to the client (Hingarh, & Ahmed, (n.d.)).
Authorization
This can best be done through pins and passcodes or biometrics where need be. Security measures can be installed on the software to guarantee the safety and security of information from malicious and ill-meaning people (Hingarh, & Ahmed, (n.d.)).
10
REFERENCES
Hingarh, V., & Ahmed, A. (n.d.). Understanding and Conducting Information Systems Auditing. https://books.google.co.ke/books?id=pXA_BaYIEHEC&pg=PA98&lpg=PA98&dq=Monitoring,+Maintenance+and+operations+of+a+banking+software&source=bl&ots=BuwTJ70E6J&sig=ACfU3U2D5jy-wRQDeZNLI3vmPetMunKnDw&hl=en&sa=X&ved=2ahUKEwio4LC0qP7pAhVBrxoKHTcFAvIQ6AEwGnoECAkQAQ#v=onepage&q=Monitoring%2C%20Maintenance%20and%20operations%20of%20a%20banking%20software&f=false
Kassaye, A. K. (n.d.). IMPROVING USABILITY OF BANKING WEBSITES [Unpublished master's thesis]. The University of Boras. https://www.diva-portal.org/smash/get/diva2:1309385/FULLTEXT01.pdf
Mamo, F. F. (2018). Assessing the Life Cycle of Projects in Commercial Bank of Ethiopia Program Management Office [Unpublished doctoral dissertation]. Addis Ababa University College of Business and Economics.
Project planning in Agile methodology. (2018, November 1). Planview. https://www.planview.com/resources/guide/agile-methodologies-a-beginners-guide/project-planning-agile/
Scope Planning. (n.d.). In Project Management. https://opentextbc.ca/projectmanagement/chapter/chapter-9-scope-planning-project-management/
