PROJECT CHARTER

C
COON
NTTE
ENNTTSS ↠WHAT ARE THE DELIVERABLES AND SUB-DELIVERABLES?
Our final deliverables will include two identical F1 in Schools India A project charter is essential to formally authorise the initiation of any project. It
cars, all three core portfolios — Enterprise, Engineering, and Project
Page 1 : Initiation process Management — along with a pit display, a ten-minute verbal
acts as a foundational document, outlining the project's purpose, scope,
deliverables, key stakeholders, constraints, assumptions, risks, and resources. It
Page 2 : Planning process presentation, an electronic copy of the specified project data, digital
engineering drawings and 3D renders for scrutineering, Annexures C
not only defines what the project aims to achieve but also sets the tone and
Page 3 : Budgeting and D, and the official F1 model block holographic stickers. We will
direction for how those goals will be approached by the team as a whole.
After our team’s official
Page 4 : also prepare a team brochure for our sponsors and a set of
merchandise, including our official team jerseys, to wear during in- kick-off meeting, we
Page 5 : Roles and Responsibilities person competitions. were ready to begin
drafting our charter. The
Page 6 : ↠WHAT ARE THE DUE DATES WE NEED TO LOOK OUT FOR? Team Manager took the
Page 7 : As regionals are scheduled for the 26th of April, we aim to complete
the car design by the end of March, or at the latest, the first week of
lead in drafting the initial
version, which was then
Page 8 : Executing and Monitoring April. All three portfolios should be ready by the 16th of April to allow brought forward at our
next team meeting. We
Page 9 : Closing Process for review and final polishing. Verbal presentations will be refined,
memorised, and rehearsed by the 19th. Team brochures will be sent reviewed the draft
to sponsors during the first week of April. together as a team in a
later meeting, making
↠ HOW DO WE, AS A TEAM, MEASURE SUCCESS, AND HOW sure each of our
WILL WE ACHIEVE IT? feedback was heard and
Success for us means staying on track with our internal deadlines, implemented. What
K
KIIC
CKK--O
OFFFF M
MEEE
ETTIIN
NGG meeting all technical and competition requirements, and presenting a follows is the final
well-rounded, professional submission. We'll also look at how well we version of our project
The evening of March 18th, the five team members of Delta V met for the first work together as a team, how consistent our communication is, and charter, created not just
time at their kick-off meeting. how strong our final branding and car performance turn out. in succession to the kick-
Feedback from judges, sponsors, and mentors will help us off meeting, but a
As first-time competitors, we were tasked with not just deliverables but also understand where we stand, but most of all, success will be knowing carefully crafted formal
understanding how each team member could work together and their strengths we put in our best and pushed ourselves to deliver something we're greenlight, which was
and weaknesses. proud of. the blueprint that shaped
But to make sure the focus stayed on the tasks we had to deliver, we our journey
simultaneously worked on a meeting agenda.
SSTTA
AKKE
EHHO
OLLD
DEER
RRRE
EGGIISSTTE
ERR
Although it was our first time meeting, the team
portrayed exceptional team synergy capabilities, and This stakeholder register helps us keep track of everyone involved in our F1 in
sticking to the meeting agenda helped prove this. Schools journey — from our team members and mentors to sponsors and judges.
It shows who they are, what role they play, how to reach them, and how engaged
As we neared the end of the kick-off meeting, we had they are in the project.
not just spent time getting to know each other, but also
had answered the six fundamental questions for By keeping this organized, we can stay on top of communication.
this project

We wrapped up by working on the stakeholder

register and the risk register survey. These also
helped when we had to divide responsibilities equally.

↠ WHY ARE WE COMPETING IN THE WORLD

FINALS?
To put our skills, creativity and collaboration to the
test – and to be crowned World Final Champions 2025

↠ WHO ARE WE DOING THE WORK FOR?

This project is being done for ourselves as a team,
for the family, friends, and mentors who’ve
supported us throughout, our sponsors who
believe in us, and our schools who have
empowered us.

P
PAAG
GEE 22
SSC
COOP
PEE SSTTA
ATTE
EMME
ENNTT
To build our WBS, we started by referring to our project charter and scope
To manage our project effectively, we knew we had to start by clearly defining the statement, along with the official competition guidelines. These gave us a clear
scope. Doing this helped us break down our deliverables into manageable tasks framework for what had to be delivered. Our Team Manager led the process by
and set clear, focused goals for the competition. Every project operates within identifying the main work packages — such as car development, engineering
certain boundaries. For us, these included our list of required deliverables, documentation, marketing, and pit display — and then we broke each of those
acceptance criteria, input from key stakeholders, a set budget, and a strict down further into specific tasks and responsibilities.
timeline. Understanding these early on gave us a complete picture of what the
project involved. This document became one of the most useful tools throughout our project. It
not only helped us stay organised, but also allowed us to assign tasks efficiently,
We used four key tools to define our scope: estimate time and resources, and monitor our progress at every stage.
A detailed scope statement
A work breakdown structure (WBS)
A preliminary timeline
A preliminary BAC (Budget at Completion)

Our scope statement was the foundation. It outlined everything we aimed to

deliver, how we would measure completion, and what success looked like. This
document was essential for scheduling and keeping the project on track.

Using the project charter and key takeaways from our kickoff meeting, we built
the first draft. Our Team Manager then called a team meeting to review it
together. This allowed everyone to share their thoughts and ensure we were all
aligned.

This system kept everyone accountable and made sure that all work met our
team’s standards and the expectations of our partners.
By taking the time to define our scope properly, we set ourselves up for a more
focused, efficient, and successful project journey.

While our project covers a wide range of deliverables and responsibilities, certain
tasks fall outside the defined scope. We will not be submitting any individual-only
work, as this competition is centred on team collaboration.
We have also chosen not to outsource any core elements such as car design,
engineering documentation, or digital media production and every component
will be created in-house to reflect the team’s capabilities.

Additionally, any features or additions that do not contribute directly to our

performance or judged deliverables have been excluded to help us stay focused
and manage time effectively.

W
WOOR
RKKB
BRRE
EAAK
KDDO
OWWN
N SSTTR
RUUC
CTTU
URRE
E
Creating our Work
Breakdown Structure
was one of the first big
steps in turning our ideas
into a clear plan. The WBS
helped us break down our
entire project into smaller,
more manageable parts,
so that each team
member knew exactly
what needed to be done
and how their role
contributed to the
outcome. This structure
made it easier to plan our
time, track progress, and
ensure we didn’t overlook
any important
deliverables.
W
WOOR
RKKB
BRRE
EAAK
KDDO
OWWN
N SSTTR
RUUC
CTTU
URRE
E
The Work Breakdown Structure (WBS) is a strategic planning tool that visually
and systematically deconstructs a project into smaller, digestible components. It
is similar to reverse-engineering success, starting from the final deliverable and
breaking it down into phases, tasks, sub-tasks, and individual actions.

For Delta V, WBS acted as our blueprint, with each level adding more detail than
the previous. Hence, we divided our WBS into levels.
↠ Top Level: The overall goal.
↠ Second Level: Breaks the overall goal into broad phases
↠Third Level: Divides the phases in level two into small and quick achievable
deliverables
C
CLLO
OSSIIN
NGG FFO
ORRM
MAALLIITTIIE
ESS SSE
ELLFF//P
PEEE
ERRA
ASSSSE
ESSM
MEEN
NTTSS
Closing is the process performed to formally complete or close a project, phase,
Self and peer assessments play a crucial
or contract. After weeks of planning, executing, and adapting, reaching this final
role in evaluating the collaborative and
stage is truly fulfilling. As a team, we started with an idea and nurtured it into a
individual contributions within a project.
fully executed project, complete with deliverables we’re proud of.
As a team, we understand that the
success of a project depends not only on
This final stage allowed us to not only wrap up the remaining work but also reflect
technical outcomes but also on how
on the entire journey. To begin with, we put together a closing presentation to
effectively team members work together.
share with stakeholders. It summarised our objectives, key milestones,
This assessment process allows each
challenges, outcomes, and overall learning. Presenting it felt like a moment of
team member to reflect on their
recognition for all our hard work.
performance, recognise their strengths
and areas for improvement, and
Reaching the end of this project has been nothing short of rewarding. From
appreciate the efforts of their peers.
brainstorming and planning to executing and overcoming challenges together,
this journey has been a mix of learning, hard work, and collaboration. The closing
Through honest feedback and reflection,
stage marks not just the completion of our project, but the celebration of
we aim to build a culture of
everything we’ve achieved as a team.
accountability, respect, and continuous
learning. It helps us identify what worked
well in our teamwork, such as
LLE
ESSSSO
ONNSS LLE
EAAR
RNNE
EDDR
REEP
POOR
RTT communication, time management,
and delegation, as well as where we may
Every project is not just about what you build, for us, but what you learn along have faced challenges. These insights are
the way. The Lessons Learned section is our opportunity to reflect on the entire essential for our growth, both as
journey: what went well, what could have gone better, and what we would do individuals and as a team, and will guide
differently in the future. This process helped us recognise key takeaways from us in improving our collaboration in
both our successes and our challenges. future projects.

To Delta V, it
was about
teamwork,
communicat
ion,
problem-
solving, and
resilience.
Documenting
these insights
allows us to
grow as
individuals
and as a
team, and
also offers a
foundation
for future
projects to
build upon.
Through
honest
reflection and
feedback, we
were able to
identify not
only how we
performed
but also how
we can
continue to
improve
moving
forward.