RISE Student Services: Software Development Project Implementation Challenges Custom Case Solution & Analysis

Section 1: Evidence Brief

Financial Metrics

• Initial project budget: 150,000 dollars allocated via external grant funding.
• Current spend: Approximately 185,000 dollars, representing a 23 percent budget overrun.
• Projected completion cost: Estimated additional 50,000 dollars to reach functional stability.
• Opportunity cost: Staff spending 15 hours per week on manual data reconciliation across four regional offices.

Operational Facts

• Timeline: Project was scheduled for 6 months; current duration has reached 18 months.
• Infrastructure: Four satellite offices currently utilize disparate Excel spreadsheets and paper records for student tracking.
• Technical Scope: The RISE system requires centralized database access, automated reporting for donors, and student progress tracking.
• Development Status: Core modules are 80 percent coded, but integration testing fails in 40 percent of use cases.

Stakeholder Positions

• Executive Director (Sarah): Prioritizes donor reporting requirements and organizational scaling; expresses growing frustration with technical delays.
• Project Lead (Marcus): Advocates for the custom-built solution; believes the unique needs of RISE cannot be met by standard software.
• External Development Team: Claims scope creep and shifting requirements from RISE leadership caused the 12-month delay.
• Front-line Staff: Distrust the new system due to previous data loss during the pilot phase; prefer manual methods.

Information Gaps

• Maintenance Costs: The case lacks data on the annual recurring costs for server hosting and technical support post-launch.
• Contractual Terms: Specific penalty clauses for the external developers regarding missed milestones are not detailed.
• User Requirements: No formal document exists that maps specific student outcomes to software features.

Section 2: Strategic Analysis

Core Strategic Question

Should RISE Student Services continue investing in a failing custom software build, or should it abandon the project in favor of a standardized platform to ensure operational survival?

• The organization faces a choice between sunk-cost persistence and strategic pivot.
• Technical debt is accumulating faster than functional utility.
• Donor credibility is at risk due to the inability to provide accurate, real-time impact data.

Structural Analysis: Resource-Based View (RBV)

An analysis of organizational resources reveals that RISE lacks the technical capability to manage complex software development. Software is a support activity for RISE, not a core competency. By attempting to build a custom solution, the organization is diverting scarce management attention away from student services, which is the primary source of competitive advantage. The current development process lacks the VRIO characteristics (Value, Rarity, Inimitability, Organization) necessary for a custom build to provide a long-term advantage.

Strategic Options

• Option 1: Complete Custom Build with New Management. Replace the current development team and appoint an external project auditor.
  • Rationale: Preserves the 185,000 dollar investment and delivers a tailored solution.
  • Trade-offs: High risk of further delays; requires significant additional capital.
  • Requirements: 50,000 dollars in new funding and a dedicated technical lead.
• Option 2: Pivot to a Commercial Off-The-Shelf (COTS) Solution. Abandon the custom build and migrate data to a proven student management platform.
  • Rationale: Immediate access to reliable features and technical support.
  • Trade-offs: Loss of custom features; necessitates a complete write-down of the 185,000 dollar investment.
  • Requirements: Data migration specialist and staff retraining program.
• Option 3: Hybrid Integration. Use the existing database backend but replace the problematic frontend with a simplified interface.
  • Rationale: Minimizes data loss while reducing technical complexity.
  • Trade-offs: Creates a fragmented system that may be difficult to maintain.
  • Requirements: Strict freeze on new feature requests for 120 days.

Preliminary Recommendation

RISE should adopt Option 2. The custom build has become a liability that threatens the core mission. Transitioning to a standardized platform ensures reliability and allows leadership to focus on student outcomes rather than debugging software. The financial write-down is painful but necessary to stop the drain on organizational resources.

Section 3: Implementation Roadmap

Critical Path

The implementation follows a 90-day stabilization and migration sequence. The transition must occur before the next donor reporting cycle to maintain funding eligibility.

• Days 1-15: Technical Audit and Selection. Evaluate three industry-leading student management platforms. Map current data fields to the new platform schema.
• Days 16-45: Data Extraction and Cleansing. Extract data from the 80 percent completed custom system and legacy Excel files. Standardize formats to ensure integrity during migration.
• Days 46-75: Pilot Migration and UAT. Execute a pilot migration for one regional office. Conduct User Acceptance Testing (UAT) with front-line staff to rebuild trust.
• Days 76-90: Full Deployment. Decommission the custom build and transition all offices to the new platform.

Key Constraints

• Data Integrity: The inconsistent formats across the four offices pose a significant risk to migration speed.
• Staff Resistance: Employees have been burned by previous failures. Adoption will be slow without visible, immediate benefits to their daily workflow.
• Technical Competency: The internal team lacks experience in large-scale data migration, requiring external temporary expertise.

Risk-Adjusted Implementation Strategy

To mitigate execution friction, the plan includes a 14-day buffer for data cleansing. If UAT fails in the pilot office, the organization will maintain parallel manual records for an additional 30 days. This avoids the catastrophic data loss experienced during the previous custom build attempt.

Section 4: Executive Review and BLUF

BLUF: Bottom Line Up Front

Terminate the custom software project immediately. RISE Student Services has fallen into a sunk-cost trap, spending 23 percent over budget for a system that is 12 months late and functionally unreliable. The internal team lacks the technical maturity to manage custom development. Transition to a standardized, subscription-based platform within 90 days. This move will stop financial hemorrhaging, restore staff productivity, and ensure accurate donor reporting. Speed and reliability must take priority over custom features that the organization cannot maintain.

Dangerous Assumption

The most consequential unchallenged premise is that the unique needs of RISE require a custom-built solution. This assumption has led to 18 months of development without a functional product. Most organizational requirements for student tracking are standard; the perceived uniqueness is an operational preference, not a strategic necessity.

Unaddressed Risks

Unconsidered Alternative

The team failed to consider a phased decommissioning. Instead of a hard pivot, RISE could have identified the one or two most critical modules of the custom build (e.g., the database) and integrated them with a third-party reporting tool. This would have saved a portion of the code while offloading the most complex development tasks to established vendors.

Verdict

APPROVED FOR LEADERSHIP REVIEW