Feedback on Luis' Team Charter

[kdea020]

What Is Good

• I like that your project is focused on your learning, i.e. "discovery" of software being the project title, and how your success criteria include your learning. :)
• I really, really, like that your Behaviour Agreement includes sharing your solutions (and difficulties!) with the class, and being supportive of new ideas. Teamwork makes the dream work!
• Overall, your charter is very good at describing how you will interact constructively with others to achieve your project mission.

  What Can Be Improved

• Needs a pass on grammar, spelling and punctuation. Some words are misspelled (for example, "intrucction" should be "instruction" under the Mission section) and not all sentences have capital letters at the beginning.
• Is your mission to "obtain instruction" on the software, or to produce a piece of software that manipulates and organises data? There's no "right" answer, of course, but you might want to consider whether the project's mission is fulfilled by your learning, or if success with your learning is a criteria that enables you to fulfill the project (as defined in the mission statement).
• Your lists of items (under Success Criteria and so on) would be much easier to read if they were bullet-pointed and on separate lines (or even had full stops!). To see how this may be done, you can look at the "raw" versions of my team charter, or of the MedSci736 one, on Github.
• For more information on Git's version of markdown (formatting), this page is a great resource: https://guides.github.com/features/mastering-markdown/
• "Respect break time start and end of classes" is a good start, but you could expand this to cover more scenarios - what about punctuality with respect to supervisory meetings etc.?
• Does "develop new skills" fit with the goals of the Behaviour Agreement section? That doesn't really describe a way of interacting with others or comporting yourself during the project. Perhaps better as a Success Criteria? :)
• You refer to "software" a lot - do you know what software you'll be using to fulfill the Success Criteria and Project Mission yet? Assuming Python, you might like to include that specifically.
• Leading on from the above, now that you have more specific knowledge about your project than when you first wrote the charter, you could re-write your Success Criteria to include more specific goals related to completing the project.
• You might want to make some of the items in the Communcation Agreement more specific, because that would give you (and the other members of your project team) a clear indication of what needs to be accomplished to fulfill the agreement (and make it easier to do so). I.e. "Make an easy way to contact you" could become "Ensure all members of the project have each others' emails".
• Also, does "Youtube and tutorials..." really belong under Communcation Agreement? If your intention was to indicate that you should access internet resources to solve a problem before contacting tutors/supervisor/classmates etc., it would probably be better to say that outright.
• As for your Project Roles, have you considered that you might also be the product owner? I.e. do you have input into what goes into your project and what counts as "complete"? Just a thought :) And don't forget that your classmates and tutors are valuable resources, too.

[Luxo736]

Awesome! 100% satisfy with this feedback I consider indeed each of your points . I would be glad you review my future repositories. thank you!!!