Skip to content

Project Delivery Process in SDLC Framework

Pragmatic Project Management: Combining Strategic Planning with Agile Discipline


Preliminary Assessment

Discovery
Phase

Implementation Proposal

Project
Kickoff

Solution
Design

User Experience Design

Agile Software Development

Quality Assurance

Beta and Final UAT

Training End Users

Launch Planning and Deployment

Post-Launch Support

Headquartered in Toronto, Ontario, Canada

Project Delivery Process in SDLC Framework


Pragmatic Project Management: Combining Strategic Planning with Agile Discipline

Book a Discovery Call

Headquartered in Toronto, Ontario, Canada

Project Delivery Process in SDLC Framework


Pragmatic Project Management: Combining Strategic Planning with Agile Discipline

Book a Discovery Call

Pragmatic Project Management Combines Strategy, SDLC and Agile

At Mantrax, we focus on pragmatic project management that blends strategic planning and the SDLC framework with agile discipline, ensuring clarity from discovery through deployment. By combining a robust upfront vision and discovery process with iterative execution, this method drives efficiency, reduces risk, and delivers value faster.

We deliver software using a structured SDLC approach: planning, design, development, testing, and deployment. Our Statement of Work (SOW) and project kick-off ensure strategic planning and proper tool setup from start to finish.

 Our pragmiatc approach to overall project management focuses on the following two pillars:

Strategic Planning
(Comprehensive Discovery + Options Analysis)

SDLC Framework with Agile Methodology 
(Strucutre + Agility)

Our Strategic Planning Framework

Our strategic planning at a high level consists of three core areas: Comprehensive Discovery, Options Analysis, and the Design of Transparent Processes.

Comprehensive Discovery

We tailor discovery to your planning journey, covering technology challenges, desired future state, and stakeholder engagement. Activities may include:

  • Project plan reviews
  • Workshops
  • Current state and future state analysis: process maps, customer journeys, user experience, etc. 
  • Market research

This ensures a strong foundation for solution design and project planning.

Options Analysis

Discovery feeds directly into Options Analysis, where we evaluate all feasible paths forward by considering:

  • Business Objectives: Immediate stabalization requirements to mid-term and long-term application  / product roadmap.
  • Total Cost of Ownership: Long-term financial impact
  • Pros & Cons: Benefits and trade-offs of each approach
  • Resource & Infrastructure Requirements: What’s needed to support the solution
  • Risk Assessment: Potential challenges and mitigation strategies
Design of Collaborative and Transparent Processes

To enhance transparency, communication, and governance, we work within your ecosystem or configure project management tools using your credentials. This gives your team direct access to:

  • Project documentation
  • Source code
  • Real-time updates

Our collaboration model emphasizes openness and shared accountability.

Our Software Planning and Development Process

Introductory Call

An initial discussion with one of our team members to understand your requirements, the urgency of the problem, and the long-term goals. 

Preliminary Assessment

New Software or AI Product Development: We review your requirements, clarify any uncertainties, present options and high level proposal.

Legacy Application: We assess your system to identify pain points, dependencies and your objectives. After understanding the requirements, we provide options for application stabilization or modernization, depending your priorities.

Discovery Phase

A Discovery Phase is essential in any of the following situations:

  • New Product Vision:  You have a high-level vision for a new software or AI product but have not documented detailed requirements.
  • Optimization Challenges: You are facing issues with an existing application and need optimization, but the root cause of the pain points is unclear.
  • Legacy Modernization: There is a need to stabalize or modernize a legacy application, but a gap analysis between the current system and the desired future state has not been completed, and modernization options have not been reviewed.

The goal of the Discovery Phase is to:

  • Fully understand all challenges and constraints.
  • Gather and analyze all relevant internal and external factors impacting potential solutions.
  • Develop a comprehensive options analysis.
  • Recommend a realistic, actionable plan aligned with your business objectives.

A Discovery Phase may not be necessary if requirements analysis is complete and you already have a detailed project scope document with a comprehensive outline of functionality, and sufficient background information.

If this upfront work has been completed, we can move directly to developing an implementation proposal, saving time and accelerating project delivery.

Implementation Proposal (SOW)

The Implementation Blueprint, also known as the Statement of Work (SOW), is a comprehensive project plan that includes:

  • Solution: Architecture diagrams and technology stack.
  • Functional Requirements: Details for functionality to be built with prioritized least for features.
  • Wireframes: Mock up for key workflows to ensure there is alignment on functional requriements upfront. 
  • Budget:  Clear cost estimates, budget allocation and recommended contingency. 
  • Timelines & Milestones: Realistic schedules for each phase of delivery.
  • Resource Allocation: Defined roles and responsibilities for the project team.
  • Risk Assessment & Mitigation Strategies: Identification of potential risks and proactive measures to address them.
  • Communication Plan: Structured approach for updates, reporting, and stakeholder engagement.
  • Detailed Project Framework: All essential components required to ensure a robust and successful implementation.

Project Kick-off

Our kickoff process includes:

  • Communication Cadence Review: Establish clear channels and frequency for updates, meetings, and reporting to keep everyone informed and engaged.

  • Team Introductions: 
    Introduce key team members, and define responsibilities.

  • System Access Setup:
    Ensure all participants have the necessary credentials and permissions to access tools, environments, and resources.

  • Project Management Tool Configuration:
    We’re happy to work within your existing project management and software development ecosystem or guide you through the setup of our recommended tools. In either case, clients maintain full control over their project and software resources. Our goal is to enable real-time tracking, documentation, and collaboration without compromising ownership.

  • Agile Sprint Planning Overview: Review upcoming sprints, define priorities, and set expectations for iterative development and delivery.

Solution Design

This solution design step begins during the Discovery Phase and continues through the Implementation Proposal. Once the project is underway, we allocate time to validate the solution design and transform project requirements into a robust technical architecture. This includes tasks such as:

  • Confirmation of Technology Selection
  • Develooping a tdatiedl e System Architecture Design and Database Design
  • Environment setup (DEV, TEST, PROD)
  • Security Design
User Experience Design

Prior to commencing any development tasks preliminary versions of the User Interface and functionalities are created utilizing wireframing tools like Figma. The user experience design entails activities including;

  • Conducting User Research; Delving into user requirements and behaviors.
  • Creating Wireframes & Prototypes; Mapping out the layout and navigation flow.
  • Establishing Information Architecture; Structuring content, in an intuitive manner.
  • Designing Visual Elements; Improving usability and visual appeal.
  • Performing Usability Testing & Iterations; Collecting feedback for enhancements.
Agile Software Development
  • Coding: Writing and implementing the software according to specifications.
  • Version Control: Managing code changes using tools like Git for collaboration and tracking.
  • Code Review: Evaluating code quality, adherence to coding standards, and identifying bugs or improvements.
  • Documentation: Writing technical documentation to explain code functionality and usage.
  • Integration: Integrating developed components/modules into a cohesive software system.
Quality Assurance & User Acceptance Testing (UAT)

Quality Assurance is built into the overall development process, for example:

  1. Approval of wireframes is required before the start of development. 
  2. Code reviews are conducted throughout the development process.
  3. Continuous functional testing by QA Analysts. 
  4. New funcationality is releasetd in TEST environment and requires client approval before deployment to PROD.

Before moving to beta, we conduct a series of stability tests to guarantee performance, security, and reliability:

  • Test Planning: Developing a plan that outlines testing goals, scope, resources and timelines.
  • Test Case Creation: Writing comprehensive test cases and scenarios to cover different aspects of the software's functionality.
  • Test Execution: Conducting both manual and automated tests based on the test plan and documenting the outcomes.
  • Defect Tracking: Identifying and documenting software issues prioritizing them by severity and monitoring their resolution.
  • Regression Testing: Repeat tests to ensure that developed and fixed features still function correctly after new changes have been made.
  • Penetration Testing: Conducted by a neutral third party to ensure the code is not vulnerable to attacks.
Beta / Pilot Release & Final UAT

The final UAT is a process of verifying the software’s readiness for production by engaging with the subject matter specialists. The testing protocols consists of test cases and scenarios. This could include:

  • Testing by the Experts: for Final User Aacptance Testing, including running boardroom simulations on end-to-end process flows and testing corner cases that are priority for the launch.  
  • Creating Test Protocols: Developing a series of test cases and scenarios to direct the testing procedure.
  • Crafting Test Plans for Subject Matter Experts: Enabling experts to formulate their test strategies tailored to their knowledge and needs.
  • Continuous Testing: Incorporating feedback, from experts to enhance the software and meet user requirements effectively.
Training

Once the final UAT is complete with the core Project Team, training will be facilitated for the end users. The training plans are developed in collaboration with the Client to accommodate end users’ preferences, skill set and availability. Training plans may include:

  • Group training
  • Written Standard Operating Procedures (SOPs) / Work instructions
  • HOW TO videos
  • User guides accessible directly from the software
Launch

The Launch or Go-Live planning is done in close collaboration with the Client, as timing and coordination of launch impacts the end users and other business activities. Meticulous planning in advance of launch, during the launch and post launch are managed by our team, including:

  • Pre-launch Preparation and Audits
  • Day 1 Planning: Crafting a schedule for the 48 hours leading up to and following the launch.
  • Risk Managemetn Strategy: Identifying risks and planning ways to address them.
  • Developing Communication Templates
  • Rolling out software following a gated approach - each step will have some prerequisites which must be satisfied
  • Monitoring & Assistance: Continuously checking system performance. Offering assistance for any problems.
  • Engaging with Stakeholders: Keeping everyone informed
  • Evaluation After Launch: Conducting an assessment to measure the sucess of the launch and pinpoint areas for enhancement.
Post-Launch Support & Maintenance

Our model is to build-operate-transfer, and supporting our client's to fully take over the management of the application and future product development roadmap. 

If rquired, we do offer post-launch support and maintenance tailored to client’s needs. Examples of post-launch activities include:

  • Updating programming languages as new versions are released 
  • Monitoring how the system is running and collecting user feedback
  • Hot fixes for urgent issues
  • Collect stakeholder feedback
  • Ensuring the application security
  • Providing additional training
  • Continuous Improvement initiatives

Connect with a Software Consultant

Book Discovery Call