Retrospective 9 14 - Herson100/ProjectOne GitHub Wiki

Joe's Retrospective

Progress so far: Learned visualforce, managed to make a beautiful page for customizing pizzas with stunning accompanying visuals. Achieved high test coverage, made large amount of progress on the presentation.

Roadblocks: N/A

Goals: Planning to sort out all of the details regarding the presentation and then focus on admin certification exam

Vi's Retrospective

What Done (Sprint)-

  • Linking up Github repository with vsCode with new Salesforce Playground
    • Kanban:(Deployable)
  • Created Checkout, CheckoutExtension, TestCheckoutExtension-97% code coverage
    • kanban:(Checkout Frame, CheckoutTest)
  • Wrote logic: total prices, track user & current cart, create cart, deleted cart
    • kanban:(Checkout- tracking User, Total Price, Logic, Deleting UnSubmitted Cart)

Problems -

  • Felt pressure developing the checkout page since it's the center point between pizza creation, navigation, after buy.
  • Lack a clear picture of what data will be passed through, what data is needed, what type of user will be accessing for query(account, user, contact)
  • Had small trouble picturing the test cases

Goals-

  • Addressing the above issue like better organization, better picture, more team discussion
  • Presentation preparation
  • Admin certification preparation

Sushil Retrospect:

  • Managed to make two pages, one for Job Listings and another to take job applications that can take file attachment to include resume
  • test code coverage reached 68% only, as there were some buttons and page links that I couldn't create test for
  • Merging to github was an issue which was resolved with team's help

Issues:

  • for this project the pages were not dependent on other teammate's pages, hence the team interactivity was lower than expected in terms of incorporating the project functionality
  • Test coverage only 68%

Future:

  • make sure the test code coverage is at least 75%
  • need to work on time management and be more productive in given time

Josh Retrospective

As a group, I don't think we did a great job with the design step for our project. Better organization for our tasks and how we assign story points to keep track of our velocity is something we need to work on as a group. I assigned very few story points to what I worked on, while other members of the group assigned a much larger number for relatively easier tasks. We need to be better about managing the kanban/story points and measuring our overall velocity during these Scrum meetings. I don't think we've discussed velocity a single time yet.

Personally, I felt that I took on too much for this project. I took on the experience site basically on my own, and I probably imposed a very harsh restriction on myself by trying to to accommodate the security limitations of the guest user profiles. There was a constant stream of issues that kept coming up with how Salesforce imposes security restrictions on these external user profiles on Experience builder pages, and I kept having to solve those issues as they came up. Looking back, I realize this wasn't the best use of my time for this particular project, as I've missed out on being able to prepare for other responsibilities like exams, admin certification, and QC.

Github was also a struggle for our group, as I didn't --nor did anyone else--seem to have a great idea about how to go about using the collaboration space appropriately. I think working within a collaborative unmanaged package in our Salesforce orgs would've made many things quite a bit simpler on this end.

I made a significant effort to communicate with my team members, but I think many of my communications went unseen/unheard/unimplemented. I think it might be a good idea for us to come up with a spot for important notes and check it daily. (Probably our Alchemy channel on the Discord server.)

I felt like I kind of had to take the reigns on a lot of things because other people were struggling so much with their functionality. I would've liked to see Joe step up a bit more on this project, since he's our current team lead and we're working on his project as a base.

My main takeaways: 1.) Be more organized, and be much more explicit about the gathering requirements step and design step of the SDLC. 2.) Collaborate on Github effectively. 3.) Don't feel like everything in a project you work on has to be perfect.

Andrew's retrospective

Should have been more organized from the start deciding how everyone's pages were going to intersect and what had to been coordinated to support that

Should have started working with the experience page first, and filled in specific requirements from the pages based on what couldn't be covered by the experience site

Code coverage ApiHandler: 100% DistanceCalculatorController: 71% LocationWrapper: 94% OrderCompleteController: 100%