Skip to content
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.

Agile methodologies and networks basic concepts training - Meeting 2 #17

Closed
2 tasks done
joaorobson opened this issue Mar 23, 2019 · 1 comment
Closed
2 tasks done
Assignees
Milestone

Comments

@joaorobson
Copy link
Collaborator

Description

Second meeting with developer team (students from Method of Software Development) and training involving basic concepts of Networks and Agile methodologies.

Phases

1 - Project (15h at the latest)

  • Talk with developers about managers decisions regarding the projects (15 min at most)
  • What are the managers considering on project selection? (5 min at most)
  • 5 minutes for each developer who want to suggest some project (25 min at most)

2 - Methodology (16:30 at the latest)

Roles (8 min at most)

  • Product Engineer (2 min at most)
  • Scrum Master (2 min at most)
  • Devops (2 min at most)
  • Architect (2 min at most)

Agile practices

  • Kanban (Zenhub) (15 min at most)
    • New Issues
    • Backlog
    • Doing
    • Done
    • Reviewing
    • Closed

Ceremonies (36 min at most)

  • Sprint (one week) (1 min at most)
  • Retrospective (5 min at most)
  • Sprint Review (5 min at most)
  • Paring (10 min at most)
  • Planning Poker (10 min at most)
  • Stand Up (5 min at most)

Tools (30 min at most)

  • Slack and "Why not Telegram?" (5 min at most)
  • Zenhub (25 min at most)

Issue (in Sprint) (10 min at most)

  • Title
  • Description
  • Label
  • Issue points
  • Assignee
  • Acceptance criteria
  • Epic (depends)

Pull Request (ready) (5 min at most)

  • Acceptance criteria accomplished
  • Build passing
  • Scrum Master evaluation
  • Keep the test coverage level, if possible

------------ HORA DA DICA (@joaorobson ) ------------
------------ HORA DO LANCHE (20 min) ----------------

3 - Basic concepts of Networks (18h at the latest)

Introduction (20 min at most)

  • IP:port
  • public IP vs private IP
  • HTTP
  • Message
  • Sending and Response
    • Response codes
  • Server vs Client
  • HTTP methods
  • Practice
    • ping
    • http.server
    • json
    • curl

Tasks

  • Each developer must be able to ping the HTTP server
  • Each developer must be able to send an HTTP request using curl

Additional Information

developers: @thiagotmb, @medeiroslucas, @VictorLeviPeixoto, @tmcstiago, @GabrielTiveron
managers: @icaropires, @Bumbleblo, @ViniciusBernardo, @joaorobson

@joaorobson
Copy link
Collaborator Author

The meeting occurred on 16/03 and both the whole developers' team and the managers' team were present. An HTTP server was created using json-server, a tool that allows you to "get a full fake REST API with zero coding in less than 30 seconds". The network concepts were taught using the whiteboard, as shown below:

IMG_20190316_183116

@joaorobson joaorobson added this to the Sprint 0 milestone Mar 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants