Working with others, Use cases & Process modelling - lecture 4
1. How to work as team
People in a team:
- Quality assurance
- UI designer
- Developer
- Documentation person
- Test engineer
- Project manager
Agile also includes a Scrum master
To be a factor as a team you should set up project management procedures
- How to deal with things that are not delivered on time
- Deal with people that don't attend
- Agreeing on deadlines
- Report, problems among the team
- How to reach a consensus, when there is a dispute in the team
2. How to get feedback and receive feedback
When should you give feedback?
When someone does something such as documentation, code, designs, ideas or test results
Why give feedback?
- You can get other peoples perspectives
- You can ensure that what you say is understood by everybody
- Prevents aspects of your design, becoming redundant
- Prevent you from making something that isn't actually needed or is bad
How to give feedback
- You could do it at synchronously via a face-to-face meeting
- Or you could do it asynchronously via reviews on a shared document
How to receive feedback
- Don't be a fucking pussy and take it
3. Understand the purpose of use cases
Something you might not have thought of is misuse cases. These are the cases when people try and mess up your product by creating too many accounts or something.
Drawn:
Written:
