User stories. Gitlab for agile development

IT1901 Fall 2020 - 7th lecture

User stories. Gitlab for agile development

  • Administrative Issues

  • User stories

  • Gitlab for agile

Groups

Group contract (1)

  • Minimum requirements for agreement:

    • Presence

    • Time spent

    • Expectations for the individual contribution

    • What happens in the event of deviations or disagreements

Group contract (2)

  • must be approved by the TA for the group

  • signed by all group members

  • and delivered together with the first group deliverable

Group contract (3)

  • more recommeded items:

    • handling differences in motivation level and ambition

    • what quality is expected, how defines the group something to be "done"

    • distribution of time between meetings / group work / individual work

    • what happens if course work needs more time than expected

Group contract (4)

  • more recommeded items:

    • delays, sickness, absence - how does the group handle these

    • meeting routines both for physical and virtual (agreement for time, agenda, meeting minutes etc)

    • general communication tools (email, phone, im etc) and response time

    • dealing as a group with deliverables and deadlines

Group contract (5)

  • more recommeded items:

    • roles

    • giving feedback to the others

    • dealing with conflicts and disagreements

    • dealing with breach of contract

    • procedure to follow if the group is not able to solve conflicts / disagreements internally

Next Deadline

  • 17th of September at midnight

    • push you last changes to the group repository on Gitlab

    • post the signed group contract on BB

About domain selection

  • choose an app / service that you know well and select a couple of features to implement during the semester

  • point is to learn by implementing these using the required architectures

  • we are not looking for quantity but for quality, so just few core features will suffice

About domain selection (2)

  • the chosen app needs to be suitable for a cloud based service

  • there must therefore be some dynamic data per user managed by the server.

  • eg. a (currency) calculation will NOT fit such a project.

  • one good starting point are the cases from the HCI course (MMI)

User stories

  • slides from 1st lecture

  • video on user stories

Gitlab for agile

  • Issues

  • Milestones

  • Task lists

  • Labels

  • Boards

  • Quick actions

Norwegian University of Science and Technology