<aside> đź•ş Welcome to Project Lead (PL) 101! This guide aims to help you understand your responsibilities and give you a complete framework for what you need to do as a PL. We are excited to see how you will lead your team to accomplish great things!
</aside>
Note: This document is not a finished product and it’s open for all of you to edit! Please improve the document to help next PLs.
Mission First
We as Blueprint members ultimately unify under one goal - achieving our mission. We place the interests of the people and partners we serve above our own. Our primary measure of success is the amount of positive impact we create through our work.
Perpetual Growth
We as Blueprint members value the academic, social, and personal growth of our peers. We constantly seek to perpetuate the cycle of learning and teaching, for our benefit and for others. We strive to offer a helping hand in times of need and push each other to succeed.
Cherish Each Other
We as Blueprint members seek to cherish our time spent together. We develop meaningful relationships that extend well beyond the scope of the organization. We value each other as individuals and appreciate our differences.
Always Innovate
We as Blueprint members recognize that change is both inevitable and necessary. We are committed to innovate and emphasize effective solutions as needed in order to remain relevant - nothing is sacred. We welcome new ideas and diverse thinking.
Be Humble
We as Blueprint members strive to remain humble, accept our imperfections, and be receptive to feedback. We approach challenges with an open mind and remember that anyone can pursue social good, not just Blueprint.
<aside> ⚠️ If CSC263 taught me anything, it’s that splitting the task in half increases the efficiency from O(n) to O(log(n)). That’s exactly why you have a partner. Split a large task into two and divide the responsibilities to make it more manageable. Leading a project is more than helping developers write code, it’s scoping project, planning timeline, hiring developers, planning events/socials, organizing weekly meetings, populating the backlog, distributing tasks, deploying your app, maintaining relationship with your NPO, all of this on top of keeping all of your developers happy, knowing at all times who is working on what, and ensuring that your project is progressing as proposed. It is a very involved process and it takes a lot of time & energy to be a good Project Lead. The first month of being a PL will be the hardest part of being a PL and it will require more work than a course. All that is to say, for your own sanity, please divide the tasks and responsibilities!!
</aside>