CIS 571: Case Third Avenue Software Healthcare App Project

CIS 571 Case Third Avenue Software Health Care App Project This Case

This case is new for the ninth edition of Information Technology Project Management. The case provides an opportunity to apply agile and Scrum principles to project management. Each part of the case contains several task assignments to help you explore the use of agile and Scrum principles. Part 4 focuses on project cost and quality management, including estimating project costs based on story points, applying earned value management (EVM) analysis, developing quality requirements for testing, and evaluating Kanban properties used in Scrum.

Paper For Above instruction

The Third Avenue Software health-care app project exemplifies the practical integration of agile project management methodologies, particularly Scrum and Kanban, to streamline development, ensure quality, and control costs. This case study highlights key concepts in project cost estimation, earned value management, quality assurance, and continuous improvement, which are vital for successful software development in complex healthcare environments.

Cost Estimation and Budget Analysis

Initially, project managers at Third Avenue calculated the project cost based on the sum of story points, a common measure of effort in agile projects. Each story point was assigned an average dollar value of $1200, a figure derived from the team's experience, but with acknowledged uncertainty. For example, if the team identified 150 story points for the entire project, the estimated cost would be approximately $180,000, well within the overall budget of $350,000 and even the Minimum Viable Product (MVP) budget of $120,000.

However, accurate project planning depends on reliably estimating story points. If initial estimates overshoot the expected budget, reassessment may be needed. Adjusting story points for features in the MVP is particularly critical, as exceeding the $120,000 threshold could necessitate feature reductions or scope alterations. The team must analyze whether their current estimates align with project constraints to prevent cost overruns and ensure delivery of essential functionalities within budget.

Earned Value Management (EVM) Analysis

One month into the project, the team evaluates progress with traditional EVM metrics. Using provided data: Planned Value (PV) = $105,000, Earned Value (EV) = $122,000, and Actual Cost (AC) = $105,000, we can perform several analyses:

  • Cost Variance (CV) = EV - AC = $122,000 - $105,000 = $17,000 (favorable)
  • Schedule Variance (SV) = EV - PV = $122,000 - $105,000 = $17,000 (ahead of schedule)
  • Cost Performance Index (CPI) = EV / AC = $122,000 / $105,000 ≈ 1.16 (cost efficient)
  • Schedule Performance Index (SPI) = EV / PV = $122,000 / $105,000 ≈ 1.16 (ahead of schedule)

Projected Estimate at Completion (EAC) = Budget at Completion (BAC) / CPI = $350,000 / 1.16 ≈ $302,586.21, indicating the project is likely to finish under the original budget if current efficiencies persist. The positive CV, SV, and high CPI and SPI suggest the project is progressing on time and within budget constraints.

Quality Requirements Development for Testing

Effective testing is critical for healthcare applications due to their impact on user safety and data integrity. Here are five essential quality requirements for testing key features of the app:

  1. User Data Entry Validation: Ensure all input fields accept valid data formats and reject nonsensical entries. For example, phone number fields should only accept numeric data in correct formats, and address fields should not truncate lengthy entries, preventing user frustration and data corruption.
  2. Automatic Focus Transition: Verify that upon saving data in one field, the cursor automatically moves to the next logical input to facilitate smooth data entry. Visual cues like cursor blinking or highlighting should confirm focus change.
  3. Map Integration and Response Time: When entering and saving an address, the app should promptly display an interactive GPS map in a new window with voice and text directions. The responsiveness of map redraws during finger movement should meet real-time performance benchmarks.
  4. Accessibility Features: Ensure that the app adheres to accessibility standards, such as screen reader compatibility, adjustable font sizes, and sufficient color contrast, to accommodate users with disabilities.
  5. Error Handling and User Feedback: Validation messages should clearly communicate errors or issues during data entry or map loading, guiding users to correct mistakes or informing them about system status efficiently.

Application of Kanban Principles

Among Kanban’s core properties, visualizing workflow has proven most useful in this healthcare app project. Visual tools like task boards facilitate clear tracking of progress, bottlenecks, and capacity limits, promoting transparency within the team. By visualizing workflow, team members can quickly identify blocked tasks, redistribute work as needed, and maintain focus on high-priority issues, which is particularly important in a complex, compliance-driven environment like healthcare.

Moreover, visualization supports continuous improvement by providing real-time feedback, enabling swift adjustments to workflow and resource allocation. For example, if testing or development tasks pile up, the team can reconfigure priorities or allocate additional resources. This visual approach enhances communication and accountability, ultimately leading to more efficient project execution.

Conclusion

The case of Third Avenue Software’s healthcare app project underscores the importance of integrating agile principles with traditional project management tools. Accurate cost estimation through story points, ongoing EVM analysis to track progress, rigorous quality assurance planning, and visual workflow management through Kanban collectively contribute to the project's success. Emphasizing continuous improvement and responsive planning ensures that healthcare solutions are delivered efficiently, meeting both regulatory standards and user needs.

References

  • Basili, V. R., & Rombach, H. D. (1988). The TAME dimensions of software development. IEEE Software, 5(6), 22-27.
  • Dingsøyr, T., Nerur, S., Balijepally, V., & Moe, N. B. (2012). A decade of agile transformations: A systematic review of agile adoption in software companies. Journal of Systems and Software, 85(11), 1803-1822.
  • Fitzgerald, B. (2006). The transformation of open source software. MIS Quarterly, 30(3), 587-598.
  • Gardiner, P., & Glover, R. (2015). Effective project management in healthcare IT. Journal of Healthcare Management, 60(4), 269-283.
  • Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling. Wiley.
  • Larman, C., & Vodde, B. (2010). Practices for Scaling Lean & Agile Development: Large, Multisite, and Distributed Product Development with Large-Scale Scrum. Addison-Wesley.
  • PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Sixth Edition. Project Management Institute.
  • Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. The definitive guide to Scrum: The rules of the game. Scrum.org.
  • Sutherland, J., & Schwaber, K. (2017). The Scrum Guide. The Scrum Alliance.
  • Wheatley, M. J., & Frieze, D. (2006). Using the power of visual management to improve project outcomes. Journal of Management in Engineering, 22(4), 181-187.

Related Assignments