hackyourfuturebelgium / bf-agile-development Goto Github PK

my fork of module repository

Learning Objectives

1. Developing HTML & CSS

• use the LiveServer extension to launch an HTML page in the browser
• use autocomplete to begin a new HTML document, create new tags, and much
  more
• use the HTML CSS Support and IntelliSense fo CSS class names
  extensions to make writing HTML & CSS more efficient
• use VSCode configurations to format your code on save
• use npm run format to format all the code in your repository
• Linting CSS: You can use the npm run lint:css script to find
  mistakes in your CSS, and you can fix the mistakes.
• Validating HTML: You can use the npm run validate:html script to
  find mistakes in your CSS, and you can fix the mistakes.
• inspect the source code of a web page using the Sources tab
• find any part of the web page in the Elements tab of your Dev Tools DOM
  inspector
• find the styles for any element in the Elements tab
• make temporary changes in a web page from the Elements tab to see how
  they will look

2. Following Plans

• Project Definition and Scope: As a group, you can agree on what you
  are trying to build, and can clearly describe the project using a README
  and a repository description.
• External: constraints that come from outside your group
• Internal, Involuntary: constraints that come from within your group,
  but your group did not decide to have one.
• Internal, Voluntary: constraints your group decides on to improve the
  quality of your development process and final software.
• Communication Plans: You can work with your group mates to agree on a
  communication plan to follow during development.
• Communicating Challenges: During development, you can discuss with your colleagues
• Using a Backlog: You can develop from a backlog of features organized
• Follow a Development Strategies: You can follow a development strategy
  to understand the code required for must-have user stories.
• Create Issues From a Dev Strategy: You can create issues for user
  stories in your project based on the development strategy.
• assess how well you worked as a group
• find ways to improve in the next project
• Compare your plan to the reality of developing your website
• track your progress with the project board
• develop your code locally on a separate branch
• Send a PR that passes CI checks and meets the requirements
• Code Review: You can both review a group mate's PR, and productively
  participate in a review of your own code.
• Match a Design & Acceptance Criteria: When developing your tasks, you
  can write code that matches the project's Wireframe and meets your issue's
  Acceptance Criteria.

3. Writing Plans

• Write User Personas: As a group you can describing your site's users
  with User Personas, and you can use the personas to plan your website from
  the user's perspective.
• Write User Stories: Given a working web page, you can describe it with
  user stories and acceptance criteria for each user story.
• Write a Backlog: After listing all the user stories for a web page,
  you can organize them into a Backlog by priority: must-have,
  should-have and could-have
• Create a Prioritized Design: Using your backlog and the original site
  as a guide, you can create a Wireframe of the site your group will build.
  You can use different colors and comments to indicate a priority for each
  component in the Wireframe.
• Write a Development Strategies: You can translate your Wireframe and
  Backlog into a Development Strategy for the must-have user stories.

4. Adapting Plans

• Adjusting the Backlog: As a group you can agree to changes in the
  backlog when necessary.
• Adjusting the Design: As a group you can agree on changes to the
  design during the development process when it becomes clear your old
  design needs updating.
• Updating the Project Board: You can manage the project board by
  adding, removing or updating issues when necessary. This includes changing
  labels, milestones, or assignees when necessary.

Week 2

• I have pushed my progress to my fork of exercises repo

I Need Help With:

What went well?

What went less well?

Lessons Learned

Me

What was clear, what did you master?

Where can you still use some help?

Where can you help others moving forwards?

The Course

What can there be more of?

What can there be less of?

What materials were most helpful (from HYF or elsewhere)?

What HYF material was least helpful?

Any suggestions for future classes?