Product Ownership & Full-Stack Engineering
sm:P
Led a cross-functional team through four Agile sprints to design, build, and deliver a full-stack mentorship platform MVP, translating evolving client requirements into production-ready features while coordinating engineering execution and stakeholder communication.
01 · Context
What existed, and why it wasn't working
A research organization wanted to improve how mentors and mentees connected throughout academic research projects. Existing workflows were fragmented, making it difficult for participants to discover opportunities, communicate effectively, and manage mentorship relationships
Our team was tasked with designing and delivering a functional MVP within a three-month timeline while continuously incorporating feedback from stakeholders throughout development.
02 · Goal
A single definition of success
Deliver a production-ready mentorship platform MVP that addressed the client's highest-priority workflows while remaining flexible enough to evolve through continuous stakeholder feedback.
How might we deliver the highest-value product within four Agile sprints while adapting to changing client priorities?
03 · Process
How the work unfolded
The project began with stakeholder meetings to understand the client's vision, identify priority user workflows, and establish the scope of an MVP that could realistically be delivered within four sprints. Regular client meetings continued throughout development, allowing the backlog to evolve as requirements became more clearly defined.
As Tech Lead, I coordinated sprint planning, managed engineering priorities using Jira, facilitated stand-ups, and helped balance feature scope against development timelines. Breaking larger goals into sprint-sized deliverables ensured the team maintained steady progress while remaining responsive to stakeholder feedback.
As new requirements emerged during stakeholder reviews, I worked with the team to refine and reprioritize features without compromising overall delivery goals — implementing across the MERN stack, from frontend components to backend REST integrations. Development emphasized reusable components, maintainable architecture, and incremental feature delivery across each sprint.
A major focus of the project involved integrating frontend interfaces with backend services to create seamless user workflows across the platform. This included coordinating API communication, validating data flow between layers, and ensuring features functioned cohesively as the application grew throughout each sprint.
The project concluded with a functional MVP presented to the client after four Agile sprints. Continuous demonstrations throughout development reduced uncertainty, enabled rapid iteration, and ensured the delivered product closely aligned with stakeholder expectations.
•Sprint 1: Requirements · Architecture · UI
•Sprint 2: Core Features · Backend APIs
•Sprint 3: Integration · Iteration
•Sprint 4: Polish · Testing · Client Delivery
04 · Key Decision
The non-obvious call
Throughout development, new client requests frequently emerged that exceeded what could reasonably fit within the project's timeline. Rather than attempting to implement every feature, I worked with stakeholders to continually reprioritize the backlog around the highest-impact workflows. This allowed the team to deliver a cohesive MVP instead of an incomplete collection of partially implemented features.
05 · Outcome
Key Functionality
The project successfully delivered a working mentorship platform MVP within the planned three-month timeline while accommodating evolving stakeholder priorities throughout development. Beyond the technical implementation, the project demonstrated the value of iterative product development, frequent client communication, and disciplined sprint planning in delivering meaningful software under real-world constraints.
06 · Reflection
What I'd do differently
Serving as both an engineer and project lead fundamentally changed how I approach software development. Rather than viewing engineering tasks in isolation, I learned to balance technical implementation with product priorities, stakeholder expectations, and team coordination. If I continued the project, I would introduce automated testing, CI/CD pipelines, and analytics instrumentation to better support future feature development and product decision-making.
07 · Highlights
Noteworthy accomplishments
• Managed backlog and sprint execution using Jira, reprioritizing against evolving client
requirements
• Led sprint planning across four Agile sprints, translating stakeholder needs into scoped,
deliverable increments
• Coordinated a cross-functional team, aligning engineering execution with stakeholder expectations
• Delivered a production-ready MVP for a real client within a three-month timeline
• Developed frontend and backend features using the MERN stack
• Integrated frontend interfaces with backend REST APIs