*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project

*** Please utilize the Kanban project methodology : please look at Scenario B attachment***

Assignment 1: (please use the project plan draft attachment)

For this assignment, you will draft a project plan for the project proposal you outlined in Week 1 (and updated earlier this week based on instructor feedback).

Create a 3- to 4-page project plan draft, based on the document provided, for the business scenario you chose last week. You may fill out the document using Microsoft Word, or other another software (such as Microsoft Excel or Microsoft Project), to create your project plan draft. Your draft must include the following items:

Network technology recommendation(s)
Database management system recommendation(s)
Appropriate software application recommendation(s)
Cloud service recommendation(s)

Assignment 2: (Please use supporting research template attachment)

Conducting research and creating a supporting research report serves two important purposes with respect to your project:

It explains your technological choices in terms of business benefits and risks. This explanation is crucial for executive approval.
It either reinforces or improves your plan–but only if you apply the results of your research to a new draft of your plan. In the industry, project managers develop their plans iteratively and change them as they conduct more research and identify better or cheaper alternatives. This iterative approach is especially relevant to IT projects because new technologies are developed and forced to retire at a very quick pace.

For this assignment, you will conduct research and create a supporting research report. Then, based on your research, you will identify and explain the rationale for three improvements to the project plan you submitted last week.

Conduct additional research on your project’s industry, recommended technology vendors, and the categories presented in the Supporting Research Report. You may want to include the Gartner Group and Forrester Research in your list of organizations to research.

Complete the Supporting Research Report template.

Create a second draft of your project plan. Highlight in yellow the three changes you made to the second draft based on the in-depth research you conducted this week, and explain why you made the changes.

Submit both your Supporting Research Report and second draft.

Assignment 3:

To complete this assignment, you will need to create the following components:

A system diagram that shows, in graphic form, the components of your project
Your system diagram should follow the system description you submitted in your Week 2 project plan (but may differ based on the research you have conducted since Week 2).
You may create your system diagram in Microsoft PowerPoint, Microsoft Visio, Lucidchart, or a graphics program of your choice.
A network diagram that shows, in graphic form, the flow of data within your project
Your network diagram should follow the network description you defined in the Week 2 project plan (but may differ based on the research you have conducted since Week 2).
You may create your network diagram in Microsoft PowerPoint, Microsoft Visio, Lucidchart, or a graphics program of your choice.
A database design document, including an entity-relationship diagram, a data dictionary, and table definitions, representing all of the data that must be stored and maintained within the context of your project and how that data is organized
A clearly articulated cybersecurity plan that explains how you plan to secure project data and processes
Source code (may be partial) for at least one software application
Your source code may be implemented in HTML/JavaScript, Java, C++, or another programming language.
Download and unzip the HTML/JavaScript/CSS sample code (attached)files for an example of a partial software application implementation.
A quality assurance and software test plan
Download the Software Test Plan (attached) for an example of what information is typically included and how it is typically organized in a software test plan.

Note: All deliverables must be portfolio ready, which means as complete and error-free as possible.

Assignment 4: Project roll-out begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project roll-out process comprises of specific steps that must be scheduled carefully to enable the project to hit production deadlines and meet business expectations.

For this assignment you will create an implementation project plan that outlines the steps involved in implementing your project. This document is sometimes called a work-back schedule because you begin with the date that your project needs to go live, and then work back from there to determine what needs to be done when.

You will also conduct a post-mortem on the work you have submitted to date. Post-mortem (from the Latin for “after death,”), when referred to it in a business context is the analysis of a project’s process and results conducted by key project stakeholders after the project has been moved into production, which means it’s functionally complete. The goal of a post-mortem is to identify what went right and what went wrong post-implementation so that project managers can apply these lessons learned to future projects.

For this assignment, you will need to do three things:

Complete a work-back schedule that presents the steps involved in implementing your project.
Conduct a post-mortem on the work you have submitted to date in this course.
Update your project documents based on the results of your post-mortem.

Review the Project Implementation Plan Example(attached).

Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software (such as Microsoft Project) to create your project implementation plan.

Download and complete the Post-Mortem template(attached) based on your experiences completing the course project over the last five weeks.

Revise the project documents you have submitted so far in the course based on your completed post-mortem.

Submit your project implementation plan, post-mortem, and updated project documents.

*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Running Head: PROJECT. 1 Internet Bank Project proposal Michelle C. Smith University of Phoenix Internet Bank Project proposal Overview Internet bank is software providing financial services electronically to enable XYZ Bank clients transact via internet i.e. the bank’s website. Internet Bank has to contain technical factors such as manageability, scalability and security. Internet bank enable clients to make payments, transfer money, check balances, obtain statements and manage financial transactions. It is important in offering financial products and services such as opening of accounts and making deposits; application of debit, credit and travel cards, loans; Insurance, investment and tax services. Internet bank is multi-channel meaning with online banking system being the major channel and other features include Mobile; Channels for Distribution i.e. SMS, fax and E-mail; Call Centers (IVR). All these features are controlled by same administrator, have same security features and can access information of the Bank. It offers complete services to private, corporate, retail and SMEs (Small and Medium Enterprises) customers. This project aims at developing technical architecture that supports business processes for Internet Bank. Scope of the project Opportunities from the Project The project will create an online presence as extension of our business. The project will increase the number of customers opening accounts and transacting with our bank. The project will ease accessibility of our services by customers since it allows clients to transact remotely without necessarily coming to the bank’s premises. The project will lead to extensive marketing of company’s existing and update customers on new products and services. The project will improve efficiency of services by reducing the number of clients who visit the banking hall. It will provide an opportunity for increased profitability as it cuts operational costs of hiring many employees. It will enable 24 hour access to bank’s service and account access. Project Objectives To provide internet presence of bank’s services and products as business extension. To improve efficiency of services offered by the bank since it is fast and easily accessible. To make service and products of the Bank to be available anywhere and at any time. To act as a marketing tool for company’s products and services. To increase profitability by reducing operational costs and also increasing client base. To increase the number of customers by wooing internet users. To make the bank competitive with other banks with internet presence. Project Methodology Technology (Technical Architecture) The software presents a solution for online banking services. It should contain account and deposit features, credit, debit and travel card services features, loans and insurance service features, investment feature and tax service feature. For success, technical features for the software application are; Scalability- architectural infrastructure should allow recruitment of new customers and at the same time offering uninterrupted services to the already signed up users. Availability- The software should be accessible all time i.e. 24 hours and 7 days a week. The services should also have best user interface. Security- Each user must be carried through a thorough process during registration for identification before any transaction and should contain multi-level authentication and security practices accepted by the industry. Manageability- The software should be easily managed by administrators, easily updated and supported. Internet bank has a database for storing records of users, bank information and system information. Application services such as deposit features and account services are business processes presented as XML web features. The interfaces allow ease of redesigning based on requirements of the bank and features of particular channels. The front-end interfaces depend on tier of application services. Integration level allows for easy interaction between the internet bank features and bank information. High-Level Schedule The project will take a total of 2 months. This development project of technical architecture will be written and completed in a week and then forwarded to the senior management and investors for review. The project report will then be taken to the designer who will design the software application who in the second week and will take about 4 weeks to prepare the project. The software application will be tested and problems addressed for one week and then launched the last week concluding our 2 month project. Designers and testers have to be paid. References Marakarkandy, B., Yajnik, N., & Dasgupta, C. (2017). Enabling internet banking adoption. Journal of Enterprise Information Management.
*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Supporting Research Report BSA/425 v1 Page 2 of 2 University of Phoenix Material Supporting Research Report Instructions: Fill out each of the sections below with information relevant to your project. Be sure to include the name and purpose of your project. Supporting Research Report for: Enter your project name here Write the purpose of your project here. Executive Summary Industry Background Technology Trends Project Approach Selected Vendors Alternative Approach Impact Analysis Cost-Benefit Analysis Financial Analysis Risk analysis Copyright © 2018 by University of Phoenix. All rights reserved.
*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Software Test Plan BSA/425 v1 Page 2 of 2 University of Phoenix Material Software Test Plan Enter the name of the project here. Describe the purpose of the project here. Features To Be Tested / Not To Be Tested Identify all features and combinations of features that will be tested. Also, describe features which will not be tested and explain why. Testing Pass / Fail Criteria Define the pass / fail criteria for each of the tests defined in this test plan. Testing Approach Describe the testing processes, testing types, and testing methods which will be used in this testing project. Discuss the testing strategy and how this testing strategy will be applied to test this application. Testing Cases Define 12 to 15 test cases for your project. Testing Materials (Hardware/Software Requirements) Identify the resources that are needed for testing in this project. Include the physical facilities, hardware, software, tools, and any other resources this project will use during testing. Testing Schedule Testing Activity Duration Resource Comments Test Plan Creation 5 days Test Manager Test Specification Creation 10 days Test Leads Test Specification Team Review 5 days Project Team Component Testing 20 days Component Testers Integration Testing 20 days Component and System Testers System Testing 15 days System Testers Performance Testing 5 days System Testers Use Case Validation 10 days System Testers Alpha Testing 5 days Product Managers / Analysts Beta Testing / Pilot Program 20 days Pilot Program End-Users Risks and Contingencies Matrix Risk Probability Risk Type Owner Contingencies / Mitigation Approach Do not have enough skilled workers to test components as they are ready for testing. 25% Project Resources Testing Manager Testing schedule will be adjusted based upon available resources. Testing team member turnover 10% Project Resources Testing Manager Adjust testing schedules. Make sure testing team members are cross-trained on testing techniques in case a team member leaves the organization. Copyright © 2018 by University of Phoenix. All rights reserved.
*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Post Mortem BSA/425 v1 Page 1 of 1 University of Phoenix Material Post-Mortem Instructions: Use the table to list the things that went well during the completion of this 5-week project and the things that didn’t go so well. Date: Project Manager (your name): Project Name: 5 Things that Went Well During the Project 5 Things that Could Have Been Done Better Below, discuss all 10 things from the list above in detail. As a project manager, or participant, what processes might you put in place to ensure the same things go well on future projects you’re involved in? What processes can you put in place to improve the not-so-great things on future projects? Be as specific as possible. Copyright © 2018 by University of Phoenix. All rights reserved.
*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Project Plan Draft BSA/425 v1 Page 7 of 7 University of Phoenix Material Project Plan Draft Instructions: Fill out each of the sections below with information relevant to your project. Be sure to include the company name associated with your project. Enter Your Company Name Project Plan Draft Network Technology Recommendations Network Technology Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Network Technology Recommendation Recommended Network Technologies Description Benefits Aggregate Selection Criteria Score Network Technology Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Network Technology Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products / Services Provided To Project Aggregate Selection Criteria Score Network Technology Deployment Challenges Deployment Challenge Deployment Challenge Description Technology Adoption Methods Method Name Method Description Cost/Benefit Considerations Benefits Costs Considerations Database System Recommendation Database System Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Database System Recommendation Recommended Database System Description Benefits Aggregate Selection Criteria Score Database System Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Database System Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products / Services Provided To Project Aggregate Selection Criteria Score Database System Deployment Challenges Deployment Challenge Deployment Challenge Description Technology Adoption Methods Method Name Method Description Cost/Benefit Considerations Benefits Costs Considerations Software Application Recommendations Software Application Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Software Application Recommendation Recommended Software Application Description Benefits Aggregate Selection Criteria Score Software Application Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Software Application Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products / Services Provided To Project Aggregate Selection Criteria Score Software Application Deployment Challenges Deployment Challenge Deployment Challenge Description Technology Adoption Methods Method Name Method Description Cost/Benefit Considerations Benefits Costs Considerations Cloud Services Recommendations Cloud Services Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Cloud Services Recommendation Recommended Cloud Services Description Benefits Aggregate Selection Criteria Score Cloud Services Vendor Selection Criteria Selection Criteria Name Selection Criteria Description Selection Criteria Value (Weighting In Points) Cloud Services Recommended Vendors Vendor Name Vendor Strengths Vendor Weaknesses Products / Services Provided To Project Aggregate Selection Criteria Score Cloud Services Deployment Challenges Deployment Challenge Deployment Challenge Description Technology Adoption Methods Method Name Method Description Cost/Benefit Considerations Benefits Costs Considerations Copyright © 2018 by University of Phoenix. All rights reserved.
*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project
Scenario B: Internet Bank you work for a startup company that is launching an internet bank. The internet bank will provide the following financial products and services to its customers: Accounts and deposits Credit, debit, and travel cards LoansInsurance Investments Tax services Senior management and investors have identified the following key technical factors for the success of the internet bank: Scalability -The technology and software application infrastructure must accommodate high growth and new users without impacting the service levels delivered to existing users. Availability -Users must be supported with robust, consistent, and reliable access; excellent performance 24 hours a day, 7 days a week. Security –Industry-accepted security practices and a multi-level authentication systems have to be put in place to authenticate and identify each user before they access their accounts and initiate transactions. Manageability –The technology and software applications infrastructure must be easy to manage, support, and update. You have been assigned to analyze your organization and develop a technical architecture to support the business processes of this internet bank.

* Please utilize the Kanban project methodology : please look at Scenario B attachment* Assignment 1: (please use the project plan draft attachment) For this assignment, you will draft a project

Company

Terms

We Accept