bf-agile-development

Agile development

What is agile?

Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a “big bang” launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.

Being agile is about learning from mistakes and constantly improving, all the details exist to make that possible The most important part of an agile project is the retrospective, it’s when you learn from your mistakes and make better plans for the future During this module, your group’s retrospective will be the most important deliverable!

Agile vs waterfall Agile

Projects

  1. All about trees

  2. Loruki

  3. HYF

Steps

  1. set up the repo

    • use this template to create a new repo on your class organization.
    • add collaborators and give them write access.
    • turn on Discussions.
    • turn on gitHub pages.
    • protect main/master branch.
  2. project definition
    • what is your project about?
    • everyone in the team should know and agree about what they are building.
    • should be added at the main README.md
  3. constrains
    • restriction that defines a project’s limitations.
    • can be internal or external.
  4. communication plan
    • how the team will communicate?
    • how you will stay in touch?
  5. user personas
    • user personas are semi-fictional characters that represent different areas of your target audience, user base or stakeholder group.
    • semrush
  6. backlog
    • collections of user stories.
    • must have
    • should have
    • could have
  7. design( wireframe)
    • a wireframe is a simplified drawing of what your website will look like.
    • excalidraw
  8. development strategy
    • translating your must have user stories to coding tasks.
    • You can do should have and could have after finishing all must have stories(if you have time).
  9. development
    • start working on coding tasks according to your development strategy
  10. retrospective
    • a retrospective is meant for looking back at how the project went and learning what to do differently next time. An incomplete project with a great retrospective is still a success.

NOTE: All these documents are living documents, which means they can be modified or changed .

This site is open source. Improve this page.