When I started this class I was somewhat worried about the capstone project. I had heard from some upperclassmen how challenging the project could be and how important it was to “pick the right team.” When I found out that I would be able to propose an organization to do my project for, however, I grew very excited about the possibility of helping the non-profit I have been volunteering for since last year – the Be a Leader Foundation. Perhaps, that was my first learning experience of this class – I learned that how difficult (or dreadful) a project is, really depends on how excited you are about doing it.
how difficult (or dreadful) a project is, really depends on how excited you are about doing it.
After my project was selected, I was very excited and wanted to make a big difference for the foundation. I contacted the project sponsor and learned that she had difficulties with the backend of their website, so I gave her my ideas on how to restructure their website to make it more user-friendly and also more appealing to the teenagers the foundation works with. Along with my team, we started to brainstorm how to make their website more likeable for teenagers and how we could revamp their social media channels while integrating all of it into their website. Nonetheless, we did most of this inventive work in isolation from the client’s feedback. We thought that if we could “surprise” our client with great ideas she would be really happy with our work – of course, that didn’t turn out well. So, the second main lesson I learned from this class is the importance of communicating with the client constantly. After having spent time and effort working on our ideas for the renewed website, we put together a draft for the Project Overview Statement (POS) and set a meeting with our client. To our surprise, during that meeting we learned that our sponsor had new plans for the website and would be hiring a company to build the website from the ground up.
We thought that if we could “surprise” our client with great ideas she would be really happy with our work – of course, that didn’t turn out well.
After learning the news from the website, our project sponsor told us about another process she had been thinking of improving somehow – the Senior Boot Camp (SBC). Our sponsor gave us some background information on the process and pointed us in the direction of using a database to improve their current spreadsheet-based system of tracking student information. After having to drop the work we had started for the website, everyone in my team felt pressured to work quickly to put together something for our Sprint 1 presentation. We decided to focus on the database while still keeping the social media component that we had been working on. Because of the time-crunch we decided to all focus on researching database options and come up with pros and cons – we then learned that this was not very efficient. This rush taught me the next two lessons I learned in this class: it is important to keep constant internal communication, and it is necessary to let things go when they are not in scope.
it is important to keep constant internal communication, and it is necessary to let things go when they are not in scope.
Because of the rush, we all ended up doing a lot of duplicated effort and researching some of the same database technologies which was ultimately counterproductive as it created stress in our group – we then realized that this issue was caused by poor internal communication. Similarly, during our first presentation, the guest grader our professor brought to give feedback in our project told us that our scope was unclear and it really seemed that we were attempting to combine two different projects into one (that is, a social media project and a database project). After this helpful feedback, we realized that we needed to let the social media portion of our project go. From this I learned that in spite of all the time and effort we had spent on this portion of our project, it is more important to have a focused scope than trying to hold-on to things that will ultimately hinder the project’s success.
a great team is not born, it is built through good communication and effort.
After having learned these valuable lessons, my team focused on communicating more often with our new contact person (the SBC process owner) and we were able to keep better internal communication. Following this strategy resulted very productive for our team and we were able to accomplish a lot more than we had before. This taught me one of the greatest lessons I’ve learned from any class – a great team is not born, it is built through good communication and effort. Although some people could have argued that our team was not “the right team” to pick, we grew through several difficulties as a team and were able to successfully deliver a project that made our client very happy.



















































