Feedback of the chris

--- Feedback of the Chris --- # Feedback of the chris Swot analysis of chris <-- Long term unfinished tasks Hard to work with you in management; --> # Good things Setup Bank account Setup Legal Good to bring in people, like Rebal Bring the moral of the group * Speaking with ppeople * Understand the tech * Team spirit * Network and recruitment * Enthusiasm * Idealist * Loyalty to people * Knowledge (trough not legal background) of dutch legal infrastructure # Bad things * Closing deals/people - follow trough * Not task, schedule or process orientatied * Stubborn, must hear no many times * Idealist, not pramatic * Doesn't listen to other, does own thing * Distracts himself and others * Prioritizing work # Opportunities * leverage network for HR and sales and opportunities * # things to improve What would you like me to do right now? * I'm committed to you like you are to me * I will lean on you a littlebit on the ADHD * I already see you taking big steps and trying to adress the problem * I can already see some major improvements * I can also see that I have developed What would you like me to do with this information * What would you Misha like to see improved? What changes we could do now: * If I didnt know about this cognitive behavoir 1. You're going to do this work, and then this is your domain 2. We devine this domain for you and things are not in this domain, we put it to the side. CGP https://www.cgpgrey.com/blog/your-theme * Don't agree with having a domain. * Don't like Micro - management * Don't like being pushed into a corned Suggestions * more of a coordinator role * Themes that you think will help * definition of done that we can measure I see where you are going with this, when I said domain I said these terms this enables you this will make you work better. When you show you can work in other domains that will make you look where that is. I want to see the best of your in this project, but I want to see the best of you in one month and the bestof you to work with. I think working with themes are making things more diffecult without discussion with our process. I can't say no to tasks i believe need to be done, but I actually don't want to do As we gain more manpower I will offload the actions I don't want to take, to those that either don't have a choice, or that like doing that specific part With stephan. its really needed in the first 2 weeks and the other students that are not in the technical team. Output: You're gonna be more of a coordinator with these students, * To be their mentor * What are you going to do be their mentor: I want to know this: * Lets do that today / Domain Domain or Theme; How we can adress some of those weaknesses. Let's just stick with the mentor team; What are you going to do to be their mentor: * Take personality tests and map our their strenghts and weaknesses * Take the personality test as imput to their tasks * Create and help with learning new technologies : Using the Odin project as a base: https://www.theodinproject.com/ and then following up with additional language specific projects * Setup and manage the Dev-Ops environment with them * Help with day to day coding issues (mostly trough rubber duck and Stackoverflow) * Coordinate their srum process * Link up tasks and objective with school objectives * Setup and manage their linkedin profiles and help boost their profiles (and tonomy as a result as well) * Be at the hackerspace with them and just have a cool and good atmosphere there * Add a regular plan for catch up with them how they are doing and feeling [ For feedback from them and feedback to them ] * (create templates and processes to this to help automate this) * (document encounters to try and ***anchor*** the process and changes) # Suggestions to Actions: * more trict in Scrum Master role, follow the habits, eat your own poison * Only ONE active tasks in processing * [ request structural change to scrum process](/EBbHC77jSWSqEiTAR7pe_g) * The one active tasks should try to be completed before **selecting** a new tasks * Tasks can be cued but should remain in the sprint backlog until added * Use domains to see if the tasks should even fall to chris or not * COO / CFO (he's have to learn, dutch finance.)  # Scrum process * We need to work on making sure the fundementals of Agile are understood * before being hard on the "scrum methodology" * Scrum "habits != Rules", scrum is a 'best effort' approach, Who has the authority to say "we need to do this now", I think if the team agrees, then this should be fine, but it should be a call to put it to review. Is this really something we coudnt see coming? How could we have seen it coming? ``` gherkin== Feature: What happens when we disagree on a task? Scenario: If the task is unclear When The scrum member is asking for clearification Then the product owner must provide thatS Scenario: If the team disagrees with taking on the task When The scrum team thinks the objective is unrealistic, doesn't have the nessecairy skills Then The product owner has no choice but to leave it in the backlog Scenario: Task is not being forfilled for several sprints When A team member under preforms or is unable to complete tasks Then The scrum master must scale down the scrum member in commitment until their commitment matches their output. ```