Lesson notes from this course https://www.linkedin.com/learning/agile-development-practices/getting-involved-early by Harrison Ferrone

Chapter 1

  1. Everyone should work together from the start - designers, developers etc
  2. Provide multiple channels of communication
  3. Share knowledge, learn from one another i.e. designers and developers ...
  4. Pick tools that you really need, start with free easy to use tools and pay only when you need to
  5. When thinking of third party tools, consider long maintenance and cost also
  6. Document - short documents like how to write a commit, longer documents on the technical design, user requirements, project decisions, high level stuff not too much detail
  7. Delay documentation until its needed - like important changes in design and methodology

Chapter 2

  1. Write code you need today, avoid anticipatory coding
  2. Follow coding best practices - use design patterns ..
  3. Avoid premature optimization

Chapter 3

  1. Set your velocity baseline to 30% of your total available working time
  2. Its a start to help you fine-tune and improve, either add more tasks or take off tasks based on your observation
  3. Take advantage of pair programming and TDD
  4. Pair programming creates shared responsibility, deals with ego, helps train new/young devs to follow best practices
  5. TDD style = Write test, write code to pass tests, refactor
  6. Make time for refactoring as part of each sprint to avoid costly changes in the future

Chapter 4

  1. Do manual and automated testing as you go, do not defer any
  2. Record and track bugs by version/sprint
  3. Address bugs ASAP
  4. Create bug fix sprints in between new feature sprints
  5. Get a good product owner

Chapter 5

  1. Use continuous integration
  2. Use a release pipeline

Image by Dirk Wouters from Pixabay