Risks and Technical Debt

Implementation Risks

  • implementation cannot be understood by future programmers
    Mitigation: inline comments, assertions, documentation and test cases
  • misunderstandings about biology or plant relationships
    Mitigation: have experts Yvonne and Pavlo included in our team.

Domain Risks

  • table design (SQL) not suitable for our domain
    Mitigation: create ER diagram, documentation about hierarchy

Technical Risks

  • hardware risks
    Mitigation: Having a second server.

Business Risks

  • unclear communication what PermaplanT is about
    Mitigation: Do releases and advertise them, landing page.
  • too small group of users
    Mitigation: it can be used at least for ourselves and by friends
  • copyright on plant data
    Mitigation: asked for permissions