Making an AGILE TEAM CHARTER in Excel (BEST things to include)

Поділитися
Вставка
  • Опубліковано 2 гру 2024

КОМЕНТАРІ • 6

  • @kabdisoheyb8505
    @kabdisoheyb8505 2 роки тому +1

    Good precipitation and explication, good luck 🍀

  • @salaheddinesalhane9613
    @salaheddinesalhane9613 2 роки тому +1

    Thank you

  • @Philippe.C.A-R
    @Philippe.C.A-R 2 роки тому +1

    I never actually been involved in agile projects. Who spearhead the creation of this document : the project manager , the scrum master ?
    In all the videos i have seen on the web the project manager is rarely mentioned for agile projects. Is there one? Would you recommend or put out a video on the role of the project manager in Agile? Thanks

    • @davidmclachlanproject
      @davidmclachlanproject  2 роки тому +4

      Great question 🙂 You'll see an "Agile project manager" called many different things, depending on the company or industry that you work in. They could be a Scrum Master, Team facilitator, Project Coach, Iteration Manager and more. Also, the Product Owner and sometimes Business Analyst will take on PM duties (i.e. schedule in a product roadmap, lead scope gathering, or enable fully funded stable teams). The team charter is created by the whole team, but the session is facilitated by that "Scrum Master" role. Hope this helps 😊

  • @mrpetu
    @mrpetu 2 роки тому +1

    It seems to me that there are a few error on the Ceremonies that you should address. Sprint planning should not last 30 min. Actually they usually takes a few hours. About the Sprint Review, it's done only once at the end of the Sprint and also takes a few hours.

    • @davidmclachlanproject
      @davidmclachlanproject  2 роки тому +2

      I love this comment, thank you. The key here is: it will depend on differences in your team, the project or products you're delivering, and the organisation. You will find they can be different, and that's why we come together and agree on them as a team. Separately, if your sprint planning is taking multiple hours I'd suggest deeper issues i.e. is the team too large? Is the product or feature too large? Is the Product Owner not keeping the backlog in a good state before the meeting? Etc. But again, that's why each project is different 🙂