Onboarding Objectives - Ground 0

Ground 0 Team Activities

Team Formation

Understand → Introduce → Explore → Form

Read, discuss, and use the team-formation process to create groups based on skills, interests, perspectives, and project needs, rather than friendship alone.

Team Initialization

Organize → Connect → Decide → Build

Establish the team’s communication, GitHub workflow, coding practices, decision-making processes, and initial project direction.

Team Practice

Communicate → Collaborate → Solve → Document

Begin practicing the behaviors expected throughout the sprint:

  • Daily checkpoints
  • Issue tracking
  • Pair programming
  • Live debugging
  • Peer support
  • Decision documentation
  • Evidence collection
  • Integration and Test policies
  • Preparing for Checkpoints and Demos

Technical & Learning Evaluation

This checklist looks beyond whether you completed a task.

Technical development includes using tools, building solutions, solving problems, learning from mistakes, and becoming more independent.

Your evaluation should show not only what you completed, but how your technical ability changed during the sprint.

Evaluation Matrix

Supply a GitHub Issue with your self-evaluation scores and one summary for each section.

Rank each area individually. Write one reflection for each section.

You do not need to write a separate response for every row.

Tools & Development Environment

ID Area Self Rank Peer Teacher
T01 Development Environment 3 + —
T02 VS Code 3 + —
T03 Git / GitHub 3 + —
T04 Portfolio / GitHub Pages 3 + —

Summary:
Describe how your ability to use your development environment changed during the sprint. Include a specific setup problem, tool, workflow, or technical process that you learned to manage.

During the sprint, my problem solving skills and knowing how to work with the SDLC workflow became much better because of consistent use of Github, VSCode, Terminal, and Open Coding Society. Helping a few others also increased my confidence with setting up the development environment and homebrew.

I’ve learned how to

  • create and use branches in github repos
  • plan outlines of projects and then execute them in VSCode
  • commit and sync
  • debug and inspect
  • use upstream branches
  • how to navigate around on localhost and deployed sites

Development & Creation

ID Area Self Rank Peer Teacher
T05 Tools & Equipment Hacks 3 + —
T06 Portfolio / Blogging Hacks 4 = —
T07 Theme / Style / Layout 3 = —
T08 JavaScript / Coding Challenges 3 = —
T09 AI Orchestration 4 = —

Summary:
Describe something you built, modified, customized, or extended during the sprint. Explain a tool, technique, coding challenge, design decision, or AI orchestration process that helped you create or improve your work.

During the sprint, I collaborated with my teammates to create our capstone project theme page, for My Good Brain. A tool that helped us create our work was integrating OCS grid components and custom buttons, instead of using a lot of CSS. We also used git operations like cherry-picking and creating branches to isolate features and manage pull requests effectively to the OCS Pages repo.

Technical Awareness & Communication

ID Area Self Rank Peer Teacher
T10 Tech / Cyber Growth 3 + —
T11 Learning Through Mistakes 3 = —
T12 Tech / Cyber Talk 3 + —

Summary:
Describe how your technical understanding and communication developed during the sprint. Include a specific example of something you learned, a mistake that changed your understanding, or a technical idea you can now explain more clearly.

My technical understanding and communication developed as I learned a few key concepts of creating and the workflow. I learned how isolating feature updates onto independent Git branches prevents unnecessary merge conflicts when contributing to shared repositories, and helps with effective git pull requests. I also learned about ensuring that our work meets everyone’s needs and doesn’t just fulfill a single or specific requirement. Moreso, while ideating for our organizations, I learned that there are a few steps to be able to work and design, and it isn’t effective to skip ahead straight to creation.

Ranking Guidelines

Rank each area based on the technical ability you demonstrated during the sprint.

0 means you have not entered a rank yet.

Start with 1 and select the level that best represents your demonstrated ability.

Rank Description
0 Not Entered — No self-assessment has been entered yet.
1 Explore — I have encountered or experimented with this technology or skill.
2 Understand — I can explain it and perform basic tasks with support.
3 Apply — I can use it independently in my project work.
4 Analyze / Evaluate — I can troubleshoot problems, compare approaches, and improve my solution.
5 Create / Extend — I can independently customize, extend, or create solutions using the skill.

Peer / Teacher Calibration: − = below self-assessment · = = consistent with self-assessment · + = above self-assessment

Before the Evaluation

  • I reviewed my Ground 0 Checklist.
  • I reviewed the technical evidence collected during the sprint.
  • I completed my self-ranking before receiving peer or teacher feedback.
  • I can support my rankings with examples from my work.
  • I identified at least one technical area where I want to improve.

Peer Perspective

With your team:

  • I reviewed technical work or evidence from a teammate.
  • I identified a technical strength a teammate demonstrated.
  • I identified a constructive opportunity for a teammate to improve.
  • My feedback is based on technical evidence or observed work rather than personal preference.

Teacher Perspective

The teacher will use working code, repositories, commits, issues, demonstrations, documentation, troubleshooting, and discussions to evaluate technical growth.

Compare the Perspectives

After the peer and teacher evaluations are complete:

  • I compared my self-ranking with my peer ranking.
  • I compared my self-ranking with my teacher ranking.
  • I identified an area where the perspectives agreed.
  • I identified an area where the perspectives differed.
  • I considered why the perspectives may have differed.
  • I identified one specific technical action for my next sprint.

Retrospective Question

What can I do now as a developer that I could not do at the beginning of this sprint?

Strongest Technical Evidence

The technical evidence I am most proud of:

TBD

The biggest technical problem I solved:

TBD

The technical skill I most need to improve:

TBD

My next technical learning goal:

TBD

Professional Evaluation

This checklist and its summaries look beyond technical tasks.

Professional development includes how you work, communicate, collaborate, respond to problems, and contribute to a team.

Your performance will be considered from three perspectives:

Self → Peer → Teacher

Evaluation Matrix

Supply a GitHub Issue with your self-evaluation scores and one summary for each section.

Rank each area individually. Write one reflection for each section.

You do not need to write a separate response for every row.

Core Behaviors

ID Area Self Rank Peer Teacher
P01 Attendance / Tardy 4 = —
P02 Work Habits 3 + —
P03 Integrity 3 = —

Summary:
Describe how you used your class time, responded to expectations, and demonstrated responsibility during the sprint. Include a specific example of a success, difficulty, or change you made.

I have used class time efficiently by focusing on incremental coding tasks and debugging active branch issues. I also demonstrated responsibility by keeping my feature commits clean and well-organized before requesting peer and teacher reviews. Moreso, I always clarify and ask questions to clear doubts and stay on track. A sucess was that I was able to persist in class and consistently complete some coding tasks

Collaboration

ID Area Self Rank Peer Teacher
P04 Communication 4 = —
P05 Help Seeking 4 = —
P06 Mentoring / Advocacy 4 + —

Summary:
Describe how you communicated, sought help, helped others, and participated in your team. Include a specific interaction or example.

I consistently communicate with my team and always try to help them, and seek help whenever required either from my teammates or the teacher. I communicate with my team whether it’s for ideating a new project, discussing and distributing tasks, or learning new things together. Moreso, I help my peers set up their development environments, resolve any of its issues, as well as explain new, technical concepts that might seem confusing at first. I’ve sought help when I have face new issues, or want to gain clarification about projects. For example, I helped my teammates set up their homebrew and VSCode.

Professional Skills

ID Area Self Rank Peer Teacher
P07 Timeliness 3 + —
P08 Persistence 3 + —
P09 Organization 3 + —
P10 Engagement 3 + —

Summary:
Describe how you managed your time, persisted through difficulty, stayed organized, and remained engaged. Include a specific example of how you responded when the work became difficult or frustrating.

I have maintained persistent effort when encountering complex Git conflicts instead of starting over from scratch. I have also organized workflows by isolating independent tasks, allowing steady progress even when roadblocks occurred. If I face a difficult issue that I can’t easily resolve, I ask my peers and teammates for help and if that doesn’t work, I ask AI for assistance and learn from mistakes. For example, when I was getting merge conflicts while working in a new branch, I learned a few methods like cherry picking to organize commits, and made sure to not give up.

Ranking Guidelines

Rank each area based on the behavior you demonstrated during the sprint.

0 means you have not entered a rank yet.

Start with 1 and select the level that best represents your demonstrated behavior.

Rank Description
0 Not Entered — No self-assessment has been entered yet.
1 Beginning — I am beginning to recognize and practice this behavior.
2 Developing — I demonstrate this behavior sometimes, usually with reminders or support.
3 Consistent — I regularly demonstrate this behavior independently.
4 Strong — I consistently demonstrate this behavior and adjust when circumstances change.
5 Model — I consistently demonstrate this behavior and help others develop it.

Peer / Teacher Calibration: − = below self-assessment · = = consistent with self-assessment · + = above self-assessment

Before the Evaluation

  • I reviewed my Ground 0 Checklist.
  • I reviewed the evidence collected during the sprint.
  • I completed my self-ranking before receiving peer or teacher feedback.
  • I can support my rankings with examples from my sprint.
  • I identified at least one area where I want to improve.

Peer Perspective

With your team:

  • I provided useful feedback to a teammate.
  • I identified a strength that a teammate contributed to the project.
  • I identified a constructive opportunity for a teammate to improve.
  • My feedback is based on observed behavior or evidence rather than personal preference.

Teacher Perspective

The teacher will use project evidence, observations, discussions, documentation, and team interactions to evaluate growth.

Compare the Perspectives

After the peer and teacher evaluations are complete:

  • I compared my self-ranking with my peer ranking.
  • I compared my self-ranking with my teacher ranking.
  • I identified an area where the perspectives agreed.
  • I identified an area where the perspectives differed.
  • I considered why the perspectives may have differed.
  • I identified one specific action for my next sprint.

Retrospective Question

What did I learn about myself as a developer and teammate that I could not have learned from a grade alone?

Next Sprint Commitment

One professional behavior I will improve:

TBD

One technical skill I will improve:

TBD

One way I will contribute more effectively to my team:

TBD

Evidence I will collect during the next sprint:

TBD

Review – “Becoming proficient in Scrum Agile Workflow”

At the end of the sprint, teams consolidate their growth and show how they’ve applied technical, collaborative, and design skills.

flowchart TD
    subgraph SR ["Sprint Review Cycle"]
        A[Team Capability Review] --> B[Peer to Peer Presentation]
        B --> C[Receive Feedback]
        C --> D[Refinement & Iteration]
        D --> E[Teacher Close-Out]
        E --> F[Individual Mastery Review]
        F --> G[Set Goals for Next Sprint]
        G --> A
    end
    
    F --> H[Personal Growth]
    

      <script>   window.PageFeatures = window.PageFeatures || {};   window.PageFeatures.grading_modules = true; </script>
HOMEWORK DELIVERY
STEP 1
STEP 2
✉ Export your solutions, then commit to submit...

Submit Failed — Enter Manually

      <!-- ASSIGNMENT SUBMISSION FORM -->

Submit Assignment 

      <!-- Lesson Chat: collapsible WebSocket chat at the bottom of a lesson page. --> <!-- Opt-in via `chat: true` in lesson frontmatter. --> <!-- Reuses the STOMP/SockJS backend from group_dashboard.html. Per-lesson scope --> <!-- is achieved by tagging messages with a [[lesson:<url>]] marker and filtering --> <!-- on the client. All lessons share a single backbone group named "lessons". -->
Lesson Chat — click to open

No messages yet.

    </div></div>
</div>

</div>

Course Timeline

                            </div>
        </div>
    </main><footer id="masterFooter" class="site-footer h-card">
<data class="u-url" href="/"></data>

<!-- <div class="wrapper">

    <div class="social-links"><ul class="social-media-list"><li>
<a rel="me" href="" target="_blank" title="">
  <span class="grey fa-brands fa- fa-lg"></span>
</a>

</li><li> </li><li> </li>

    • </ul> </div>

    </div> -->

<!--<p style="font-style: italic;">OpenAesthetic v3.0rc1.1</p>-->

<div class="footer-links">
    <div class="footer-previous">
        
    </div>

    <div class="footer-home">
        
    </div>

    <div class="footer-next">
        
    </div>
</div>

    </footer> 

        // Convert fenced code blocks to mermaid divs
    document.querySelectorAll('pre code.language-mermaid').forEach((block, index) => {
        const content = block.textContent;
        const wrapper = document.createElement('div');
        wrapper.className = 'mermaid';
        wrapper.id = 'mermaid-' + index;
        wrapper.textContent = content;
        block.parentElement.parentNode.replaceChild(wrapper, block.parentElement);
    });
    
    mermaid.run();
}); </script></body>

    </html>