Client and Developer Team Project Final Report

Client Report - Project 10

For my client role, I was the client for Project 10. My lead developer was Mikel Martinez Garcia, and the junior developers assigned to my site were William Birch and Alfredo Sanchez. The site link is: Project 10 Client Site.

For my site plan, I chose content and images that would fit my personal website and show a creative, professional style. I wanted the site to feel like me, so I provided page ideas, written content, photos, and direction for the overall look. Later in the project, I also gathered and sent more photos so the developers had more options to use.

Communication as a client was mostly okay, but there were some bumps. Some team members did not always communicate quickly, and a few things were not finished the way I had hoped. I tried to give feedback and provide what they needed without taking over too much. That part was harder than I expected because it is very tempting to want to jump in and fix everything myself.

The final site looks pretty good overall. It is not 100 percent exactly how I would have made it, but that is also part of working with a team. For the most part, everyone did their jobs, with the exception of a few things. I learned that being a client means giving clear direction, being patient, and accepting that the final result may not match every detail in your head.

Lead Developer Report - Project 2

For my lead developer role, I led Project 2 for my client, Carissa Jager. The junior developers on my team were Mikel Martinez Garcia and Jake Johnson. The site link is: Project 2 Lead Developer Site.

As lead developer, I created the GitHub repository, set up the file and folder structure, created the homepage, connected the navigation, added the CSS, published the site through GitHub Pages, and communicated with the junior developers about their child pages. I also checked the live site and made sure the shared CSS worked across the pages.

Communication with my client went well. She gave feedback and approved the site, which felt good after all the work that went into it. Communication with the development team was a little harder at times. Some responses came very late, and one page still needed more work for part of the project. I tried to follow up, stay patient, and keep things moving.

Publishing the site with GitHub went pretty well because I had already worked through some of those issues earlier in the course. I still had to check links, file names, image paths, and the live URL carefully. Managing the site helped me feel more confident with GitHub and with organizing a real website project.

Junior Developer Report - Project 1

For Project 1, I worked as a junior developer for lead developer Dorsey Jo Crowther on Alfredo Sanchez's site. My assigned child page was "The Edit." The site link is: Project 1 Junior Developer Site.

I communicated with my team lead and worked on the page I was assigned. I knew what was expected because I had my assigned child page, and I made sure it connected to the shared navigation and stylesheet. I also checked that the page matched the rest of the site as much as possible.

There were a few issues with CSS and navigation on this site, so I helped more than I originally expected. Even though I was a junior developer, I edited some extra code because the site needed it. I was happy to help, but it also reminded me that team projects can get messy when everyone is working at a different pace.

Junior Developer Report - Project 4

For Project 4, I worked as a junior developer for lead developer Karina Winn on Dorsey Jo Crowther's site. My assigned child page was the Registry page. The site link is: Project 4 Junior Developer Site.

For this site, I updated the Registry page and made sure it matched the style of the homepage and the rest of the site. I worked on the layout, spacing, fonts, images, colors, and overall design. This site came together nicely, and the client gave positive feedback.

I was able to contribute to this site without too many problems. The shared CSS helped a lot because it made the child page feel connected to the rest of the project. This part of the project showed me how much easier a team site is when the design direction is clear.

General Experience and Reflections

The most challenging part of this project was not really the coding itself. It was the teamwork and communication. For the most part, everyone did their jobs, but there were still a few issues with late communication, unfinished details, and pages that did not look exactly how I imagined they would.

I had to remind myself not to do everything myself. That is honestly hard for me. When I can see what needs to be fixed, I want to just fix it. But that is not always the best choice in a team project. I needed to let other people do their parts and not micromanage every little thing. You can lead a horse to water, as they say.

What I enjoyed most was seeing the sites start to look like real websites once the CSS was added. The difference between plain HTML and a styled site is huge. It was also nice when communication improved and the teams started coming together more near the end. The sites look pretty good overall. They are not 100 percent like I would want them, but that is how it goes sometimes when a project is shared by a team.

If I could do the project again, I would communicate expectations even earlier. I would also check in more often before the deadline so problems could be fixed sooner. I think having clearer deadlines for each page would have helped too.

After this experience, I do feel more confident working on real-world projects. I learned more about GitHub, CSS, file organization, teamwork, client feedback, and publishing a site online. The project was not perfect, but that actually made it feel more realistic. Real projects have people, delays, opinions, and unexpected issues. Overall, I am proud of the work I completed and the way the sites came together in the end.