CIS443_Week_6_Assignment_Craig_Wayman

docx

School

Strayer University *

*We aren’t endorsed by this school

Course

443

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

7

Uploaded by C.WayII

Report
Week 6 Assignment: Agile Delivery Framework Craig Wayman CIS443 Professor Alma Miller
Project Name: Home Repair Store Website and Application Level WBS Task Description Start Date Finish Date Duration (days) 1 1.0 Project Initiation 2/1/2024 3/1/2024 30 2 1.1 Government approvals 2/1/2024 2/14/2024 13 2 1.2 Setting up site office 2/1/2024 2/26/2024 25 2 1.3 Internal and customer kick-off meeting 2/2/2024 2/3/2024 1 2 1.4 Collection of stakeholders requirements 2/4/2024 2/29/2024 25 2 1.5 Fesability survey 2/1/2024 3/1/2024 29 2 1.6 Material ordering and delivery 2/1/2024 3/1/2024 29 2 1.7 Project charter signing 2/29/2024 3/1/2024 1 1 2.0 Project Planning and Design 3/2/2024 5/1/2024 60 2 2.1 Conceptual design 3/2/2024 3/12/2024 10 2 2.2 Preliminary design 3/12/2024 3/22/2024 10 2 2.3 Final design 3/22/2024 4/1/2024 10 2 2.4 Create project schedule 4/1/2024 4/16/2024 15 2 2.6 Create project execution plan 4/16/2024 5/1/2024 15 1 3.0 Project Execution 5/2/2024 7/1/2024 60 2 3.1 Develop website 5/2/2024 5/12/2024 10 2 3.2 Develop application 5/2/2024 5/12/2024 10 2 3.3 Programing 5/13/2024 6/12/2024 30 3 3.3.1 Website 5/13/2024 5/28/2024 15 3 3.3.2 Application 5/28/2024 6/12/2024 15 2 3.4 Testing and troubleshooting 6/12/2024 7/1/2024 19 2 3.5 Security Testing 6/12/2024 7/1/2024 19 2 3.6 Compatability assessment 6/12/2024 7/1/2024 19 1 4.0 Project Completion Phase 7/2/2024 8/1/2024 30 2 4.1 Final testing 7/2/2024 7/17/2024 15 2 4.2 Site clearance 7/15/2024 7/29/2024 14 3 4.3.1 Delivery to customer 7/29/2024 8/1/2024 3
Product Vision The Homes Depot Company is expanding its online and mobile presence to better serve our customers. The product vision is to provide everyone with easy, simple access to home repair materials and experts, helping you build your future one tool at a time. To support this vision, we will be using state-of-the-art in-house software and cloud resources. We take pride in the products we provide to our customers because we know you take pride in your work and a job well done. According to an article by Robin Schuurman, “The product vision describes the purpose of a product, the intention with which the product is being created, and what it aims to achieve for customers and users.” (1). I like to add that it also is a source of motivation in some instances. A shared vision is powerful and can improve how the project team works together. In this case, the Homes Depot Company wants to develop a website and mobile application that improves customer satisfaction and has a functional interface. By simply stating that we may not get the “buy-in” we want from the project team. To help build team buy-in, I like to develop a vision that evokes passion and emotion in the team. The vision I have developed for this product does both hopefully. I will employ several methods when utilizing my envisioning practice. First I would gather the key stakeholders and product owner together and develop a shared vision. As previously mentioned, this creates buy-in from the team. Following this I would want to run a brainstorming session with our entire team and workshop various ways to approach this project and any problems that may arise. This gets everyone thinking and using their creativity to develop the project. In the end, we will be able to develop an all-inclusive list of agreed-upon solutions for various project concerns. By conducting this process, we are essentially executing a dry run of the project and identifying areas of concern that we can address before they become a concern. I would also like to point out that this process is not a one- time meeting, but rather a continuous effort to ensure all hazards or concerns are addressed before they become an issue and impact the delivery of the project.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Agile Project Team Roles Agile project teams are composed of individuals from different functions who work together to complete projects in sprints, or short segments that are easier to accomplish. The team operates around the principles of self-organization, meaning individuals on the team have to take on responsibilities that are specific to their field of expertise. “There are several important roles in an Agile team, including the product owner, developer, and scrum master.”(2) The product owner manages the product roadmap and prioritizes the backlog. They also define the product vision and manage the stakeholders. They have the authority to make key decisions and are responsible for making sure the team is functioning following the project plan and schedule. The developer is responsible for programming, testing, and debugging the product. In the case of this project, we will have multiple developers working on various parts of the project. Developers play a key role in the project as they are the “builder” of the website and the mobile application. The Agile project manager is another important role. They act as coaches to the rest of the team, facilitate daily stand-up meetings, and oversee planning meetings where they help to keep the team focused and prevent scope creep. Agile project managers are here to alleviate some of the pressure placed on the product owner and other project leadership. When it comes to whether a product manager should come from an IT-related field or not, there's no 100% correct response. In my opinion, there is very little difference between a regular product manager and an IT product manager. The key difference lies in the environment they work in. Ultimately, whether the product manager should come from an IT-related field or not depends on the specific needs of the organization and the product specifications. For this project, I would want to have someone familiar with the IT field. I am delivering an IT-related project that will require someone who can speak the IT language and field questions from stakeholders. Could these things be learned by a non-IT product
manager, sure. But why would a company want to waste the money on that when they could pay for the subject matter expert? Iteration in This Project In the realm of website and mobile app development, iteration plays a vital role in achieving desired outcomes. Agile methodology prioritizes continuous feedback and collaboration between team members and stakeholders throughout the development process. Based on my research and experience in this field, iteration involves repeatedly testing and refining the product until it meets the user's needs and expectations. This process typically includes prototyping, user testing, and feedback collection, which allows developers to detect and address issues early on, ultimately saving time and resources. Based on an article by Cassandra Naji, who states, “For example, in mobile app development, iterative prototyping is a cost-effective way to build, test, iterate, re-test, and re-build quickly.”(Rehkopf,3) This approach enables developers to define the unique selling proposition (USP) of the app, map out the ideal user using storyboarding, user scenarios, and story-mapping, and gather, manage, and validate requirements using a prototyping tool. For this project, we will have many rounds of testing and re-testing to ensure the product meets or exceeds the customer's needs. When building any kind of virtual platform, testing is pivotal to the success of the product. Every action that is included with our website or mobile application must be tested to ensure it is functional. We will continue to use iterative processes to ensure we remain on track with project goals, budgets, and timelines. Source: The Importance of Stories Stories are an essential part of the Agile delivery framework. “They are short, simple descriptions of functionality told from the user’s perspective and written in their language. Stories provide just enough information for business and technical people to understand the intent.”(3). Stories are important in the
Agile delivery framework for several reasons. First, they help to keep the focus on the user and solve problems for real users. Second, they enable collaboration between users and developers, where both sides can agree enough to work together effectively and efficiently. Third, stories give us an improved understanding of the scope and progress of the project. User stories are not necessarily what they sound like, they are more like refined lists of issues that are in a “story” format to make them easier to remember. For this project, I will provide some of the examples I would use. For instance, as a user, I would like to be able to search for a product by brand so I can find what I need quickly. Essentially this is a user story that implies the customer needs to have this functionality as a requirement. It exposes you to the customer and their needs in a simple story format. Another example might be, as a user of the application, I would like to have access to my entire purchase history for tax purposes. Here we see yet another requirement broken down into a “story” format to help the team remember it.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Sources 1. Robbin Schuurman. November 29, 2017. 10 Tips for Product Owners on the Product Vision. https://www.scrum.org/resources/blog/10-tips-product-owners-product-vision . 2. Cassandra Naji. August 1, 2016. Iterative Prototyping in the Mobile App Development Process. https://www.infoq.com/articles/mobile-app-prototyping/ . 3. Max Rehkopf. No date. User stories with examples and a template. https://www.atlassian.com/agile/project-management/user-stories .