Part 4 MIS 4310 Project

1

10

Part Three

Faiz Lakhani

11/28/2023

MIS 4310

Overview

It is necessary to adopt a flexible approach to scheduling if one is to create healthcare applications because of the need for adaptation and stakeholders' participation within the framework of agile project management. As a solution to the issues raised by management about our capacity to meet deadlines, control costs, and make efficient use of the resources at our disposal, we have concluded that our project team needs two more members. Aziz, a former programmer who is now a Quality Assurance tester, and Barry, a native of Third Avenue who is an accountant, have both just joined our team. The precision of our project timeline will be improved due to their labour, and it will be easier for us to stay within our budget constraints.

Assign Story Points

Assigning story points to our user and technical stories is the first step in creating an efficient timetable for agile projects. Story points are a non-specific way of evaluating how much work is involved in a certain scenario. Factors like work difficulty, potential danger, and available time are often used to determine these relative values. Using the original programmer's estimations and our evaluations of the difficulty and work involved, our project team has allocated tale points to each narrative. By doing this, we can better understand the whole burden.

User/Technical Story	Story Points
User Story 1: Medication Tracker	5
User Story 2: Electronic Address Book	3
User Story 3: Emergency List	4
User Story 4: Emergency Information Storage	2
User Story 5: Resource Feature	3
User Story 6: Payment Feature	4
Technical Story 1: Secure Data Storage	5
Technical Story 2: User-Friendly Interface	3
Technical Story 3: Medication Tracking System	4
Technical Story 4: Secure Data Storage for Contacts	2
Technical Story 5: GPS Mapping System	4
Technical Story 6: Secure User Profile System	3
Technical Story 7: Integration of External API	5
Technical Story 8: Secure Payment Gateway	4

Develop a Detailed Schedule

Story point allocation is a major development milestone because it paves the way for a more precise and comprehensive timetable for the Minimum Viable Product (MVP). We have built a system for prioritizing and estimating the work needed for each feature or activity in the project by using narrative points. We can now see the full extent of the next tasks more clearly. Now that the plot elements are established, we can work on a more detailed timetable for the MVP. Tasks, their due dates, and any interdependencies between them will all be spelt out in this schedule. By working the narrative points into the calendar, we can ensure that everything is being done correctly and that enough time is spent on each feature. The minimum viable product timetable provides a guide. The proposed timetable will include a detailed list of activities, their expected timespan, and any interdependencies (Singh, 2021). The schedule will be more useful to everyone involved in the project if it has these essential components. As a result, everyone involved in the project will have a clearer picture of what has to be accomplished and in what order.

Moreover, the plan will aid in assigning resources and managing expectations by specifying projected durations for each job. Due to its adaptability and iterative nature, the Agile methodology has seen explosive growth in project management. In agile project management, work is broken up into chunks of time called "sprints," with an average length of two weeks. During these iterative periods, teams carefully choose which user stories to work on. Tasks within the project may be completed with more efficiency and precision thanks to this method of careful selection. Organizations may improve their project management techniques and successfully deliver useful results by embracing Agile principles. In project management, each sprint's successful conclusion is a major achievement. Within agile techniques, "sprints," or time-boxed iterations of work, are essential building elements.

Sprint 1 (2 weeks)	User/Technical Story
	User Story 1: Medication Tracker
	User Story 2: Electronic Address Book
	Technical Story 1: Secure Data Storage
	Technical Story 2: User-Friendly Interface
Sprint 2 (2 weeks)	User/Technical Story
	User Story 3: Emergency List
	User Story 4: Emergency Information Storage
	Technical Story 3: Medication Tracking System
	Technical Story 4: Secure Data Storage for Contacts
Sprint 3 (2 weeks)	User/Technical Story
	User Story 5: Resource Feature
	User Story 6: Payment Feature
	Technical Story 5: GPS Mapping System
	Technical Story 6: Secure User Profile System

Realism of MVP Schedule Assessment

When looking at the timeline for the MVP, it becomes clear that the goal of finishing the MVP in the first six weeks is achievable. The Minimum Viable Product (MVP) is essential to any product or service's development cycle. It has a collection of simple functions, allowing for rapid product development and market testing. The minimum viable product development team is well-staffed, with specialists with the requisite competence to complete the project successfully. Delivering a product with the most essential features and functionality, which benefits the end customers, is at the heart of the minimum viable product concept (Singh, 2021). The development team can guarantee that the product will be ready for launch within a reasonable timeline if it prioritizes moderate to low complexity features.

This method facilitates rapid iteration and user input, which is crucial to the product's development. The competence and experience of the team building the MVP is crucial to its ultimate success. The importance of assembling a team is that With the Agile methodology, we may build upon the success of the Minimum Viable Product (MVP) in a continuous and iterative process that yields development. Creating trustworthy and simple healthcare apps is more important than ever in today's high-tech world. We must find a compromise between delivering the software on schedule and making sure it is as user-friendly and secure as possible as we go forward with its development. Putting the end user first is a must at all development and design stages. An easy-to-use healthcare app will improve the user experience and increase the likelihood that the app will be used regularly. Users' demands may be better understood using user-centered design practices like usability testing and user research.

Plan Release Schedule for Subsequent Iterations

Beyond the release of the Minimum Viable Product (MVP), there is some wiggle room in the software development timetable due to customer input and changing needs. It is usual practice to make alterations to a project as it develops to meet the evolving requirements and tastes of the target audience. In his book "The Lean Startup," Eric Ries popularized the phrase "minimum viable product" to describe the first version of a product with just the most essential functionality. This methodology facilitates iterative development and testing, from which useful insights may be drawn. Planning a release schedule for future versions requires looking ahead while being flexible. This requires monitoring what is coming down the pipeline while adapting to new circumstances. To guarantee future iterations' success and on-time delivery, businesses must balance planning ahead and being flexible in their release schedules.

· Sprint 4-5 (4 weeks): Incorporate user feedback and improvements based on MVP testing.

· Sprint 6-8 (6 weeks): Add online health information, incorporating user suggestions.

· Sprint 9-11 (6 weeks): Develop payment tracking feature and address user feedback.

· Sprint 12-14 (6 weeks): Focus on usability improvements and final testing.

· Sprint 15 (2 weeks): Prepare for the app's launch, ensuring a polished final product.

Gantt Chart

Task	Duration
MVP Development	Six weeks	42
User Feedback & Iteration	Six weeks	42
Online Health Info	Six weeks	42
Payment Tracking	Six weeks	42
Usability Improvements	Eight weeks	56
Final Testing	Two weeks	12
Launch

References

Piedrahita, C., Alzate-Espinosa, G. A., Herrera-Schlesinger, M. C., Naranjo-Agudelo, A., Araujo-Guerrero, E. F., Torres-Hernández, C. A., & Benítez-Peláez, C. A. (2023). Scrum methodology adaptation in the non-software industry: agile management of a research initiative.  International Journal of Agile Systems and Management,  16(3), 368-399.

Singh, H., & Williams, P. S. (2021). A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide. In  Project Management Institute.