Plans Week 9

Focus on PBL - Commitment to your Agile Development process and tangibles.

  • Monday: Review Student Led Homework (Period 2?) and Blog
  • Tuesday: Student Presentation
  • Wednesday: Student Presentation
  • Thursday: Show FE to BE working, Script for Video
  • Friday: Student Presentation

Team

Prepare for Teacher project audit. Also, analysis of the following will speed Scrum Team plan, work, improve quality, and make a better N@tM final.

API Frontend to Backend Overview

Show demo of work in progress.

  • Must use API across multiple systems
    • Create a HTML Frontend table or view fetching from Backend using an Spring API
    • Show writing to Database

Scrum Master

Describe Program Purpose and Function. Also, highlight key system used to track, collaborate and review software.

  • Identify and Apply a Software Development process.
    • Describe your Software Development Life Cycle
    • Describe how you plan, track sprints, track features, track milestones, and assign versions.
    • Highlight Agile process: research, design, coding, testing, review, repeat.
  • Define and analyze systems and software requirements.
    • Define Computer Systems you have or will develop.
    • Indicate Tools or Automation you will use improve tracking requirements (ie Project/Scrum Board).
    • Define strategies that enable Team to target the specific needs of the customer (ie Product Owner). Describe meetings, demos, and how you collect feedback.
  • Test and Demo Software during each Sprint
    • Consider using GitHub Issues to support this process.
    • Develop and describe expectations of each feature.
    • Use feature, expected outcome, and the minimal amount of code each feature.
    • Document accomplishment with tangible evidence.
    • Have feature reviews, demos, and obtain feedback (team and/or customer)
    • Update and derive new features and tasks for next step in Software Development Life Cycle
  • My suggestion is this person helps with Frontend development

Frontend Developer

Describe Frontend designs and coding techniques.

  • Create and implement an effective frontend between humans and technology
    • Show frontend design artifacts (wire frames)
    • Describe any consideration you have made for customer requirements.
    • Indicate accommodations you have made for English Language Learners or those with Disabilities
    • Show any screens that are currently developed.
  • Describe Code and Styles Frontend development
    • HTML, Markdown, JavaScript
    • Cards, Tables, Blogging
  • Comments. Be sure to illustrate developers comments in code and how this will facilitate current and future understanding of the key portions of system.

DevOps Engineer

Describe the technical systems and processes used to ensure the ability to do continuous updates and integration of software.

  • Describe software and programming tools
    • Identify authoring tools (IDE’s, Docker, GitHub) used
    • Describe and/or show visuals of interactions and integration of programming languages, protocols, and data within project. For instance, deployed systems of Docker Images, Nginx, DNS hosting the application.
    • Describe and/or illustrate key Web Applications, APIs, and dependency systems that will be required to complete this system (Diagram).
  • Describe GitHub branch management and sociology used to ensure ability to perform continuous builds and integrations.
    • GitHub projects
    • Branching Strategies
    • Deployment processes and automation
  • Describe how to validate and test the complete system
  • My suggestion is this person helps with Backend development

Backend Developer

Describe backend coding and requirements.

  • Develop data, data types, databases, and APIs.
    • Identify authoring tools (IDE’s, Postman) used.
    • Describe and/or illustrate key data types, data structures (Lists, Dictionaries), objects, files, or databases that will be used (Flow Chart/UML).
    • Describe use of Lists or Dictionaries, database, tables, attributes, records, and systems of access (JSON, Lists, Dictionaries).
  • Comments. Be sure developers use comments in code to facilitate current and future understanding of the key portions of system.

Hacks (Video 1). Recommend… Minimize talking, minimize mouse movements, and share Tangibles.

Make a less than 4 minute video. Each individual should talk in video, code, and make their part of the video. Consider crossing over to other tables and share methods and methodologies of those working on similar roles.

  • Scrum Master should make sure all things come together.
  • DevOps should ensure there is a working project to Demo at all times.
  • Everyone should complete their part(s).
  • Everyone should help other Team Members when struggling.