AxisAgile
AxisAgile
  • 14
  • 42 437
Agile Backlog Tools for Jira
Quickly and easily refine your Product Backlog in one spot using industry best practice, built for Agile and Scrum teams.
มุมมอง: 1 850

วีดีโอ

5.3 Daily Scrum Tips
มุมมอง 2726 ปีที่แล้ว
In this video, we will be discussing some tips for the Daily Scrum answering questions such as: - Why the Daily Scrum should be conducted standing up? - How to handle tangential discussions that inevitably arise during the activity? - How can you stop team members ‘reporting’ to the ScrumMaster? - How you can keep everyone on their toes?
6.3 - Retrospective Focus Areas
มุมมอง 3816 ปีที่แล้ว
In this video, we will be discussing some focus areas for your Retrospectives, answering questions such as: - Why you shouldn't skip Retrospectives? - Should your Product Owner attend the Retrospective? - How to get your teams ready for the Retrospective? - What are some areas to focus on during the Retrospective?
2.6 How to Control Impediments
มุมมอง 6917 ปีที่แล้ว
In this video, we will be focusing on how to deal with your Scrum impediments, with a handy acronym you can use to maintain ConTROL.
4.5 Transitioning to Relative Estimation
มุมมอง 2137 ปีที่แล้ว
In this video, we will be focusing on transitioning to relative estimation, answering questions such as: - What are two significant advantages to using historical work to transition to relative estimation? - How do you leverage historical work to estimate your future work? - Where do you start?
6.4 Scrum Retrospective Techniques
มุมมอง 32K7 ปีที่แล้ว
In this video, we will be focusing on applying some Scrum Retrospective techniques, answering questions such as: - How do you set up each of these techniques? - How do you make these techniques work well? - How do these techniques tackle the classic four questions?
2.2 Sprint Planning Execution
มุมมอง 4947 ปีที่แล้ว
In this video, we will be focusing on Sprint Planning execution, answering questions such as: - What are the two parts to Sprint Planning? - How do you know how many stories to bring into Sprint Planning? - How are time estimations helpful? - When to use 'velocity-based' planning? - When to use 'commitment-based' planning?
2.1 Sprint Planning Preparation
มุมมอง 4887 ปีที่แล้ว
In this video, we focus on Sprint Planning preparation, answering questions such as: - How can Sprint Planning build great Scrum team chemistry? - What Sprint length do most teams use? - How do you decide on the right Sprint Length? - Why you should avoid changing your Sprint length? - What should be factored in in when calculating your team's Sprint Capacity?
4.3 Mechanics of Planning Poker
มุมมอง 2247 ปีที่แล้ว
In this video, we will be focusing on the mechanics of Planning Poker, answering questions such as: - Why is it called Planning Poker? - What is a common point system used for Planning Poker? - How does a Planning Poker session work? - How do you make a Planning Poker session run smoothly?
2.5 How to Define Scrum Impediments
มุมมอง 3.6K7 ปีที่แล้ว
In this video, we will be focusing on how to define an impediment, answering questions such as: - What's the difference between a block and an impediment? - What typically happens when a team encounters a block within a Sprint? - What are common impediments that Scrum teams face?
4.2 Applying Relative Estimation
มุมมอง 3687 ปีที่แล้ว
In this video, we will be focusing on applying Relative Estimation, answering questions such as: - What are the three things that you should factor into your estimates? - How much detail is needed to estimate relatively? - How is velocity calculated? - What might cause your velocities to fluctuate? - What are some simple options for calculating indicative velocities?
4.1 Understanding Relative Estimation
มุมมอง 1.4K7 ปีที่แล้ว
In this video, we will be focusing on Understanding Relative Estimation, answering questions such as: How do you estimate and more importantly, how do you rapidly re-estimate requirements that are emergent? Why is estimation painful? What unforeseen factors impact your estimates? Why bother estimating at all? Where is relative estimation best applied? What’s a good analogy you can use to explai...
Masterful ScrumMaster - Agile Australia 2012 by Ilan Goldstein
มุมมอง 1977 ปีที่แล้ว
As a ScrumMaster, Iteration Manager (or any other type of servant-leader) you form part of a new generation of enlightened professionals. This role is deep and complex, yet judging by the numerous discussion groups and job classifieds, there is a lack of emphasis on what really matters when identifying worthy representatives. There is significant discussion surrounding the prospective roles and...
1.0 Welcome Applied Scrum Activities
มุมมอง 917 ปีที่แล้ว
Learn a range of tools and techniques to more efficiently facilitate your Scrum activities to keep them fresh while continually delivering value.

ความคิดเห็น

  • @maxzytaruk8558
    @maxzytaruk8558 2 ปีที่แล้ว

    This helped me so so much for my stats class!

  • @faab1234
    @faab1234 5 ปีที่แล้ว

    awesome explanation the way you explained is quite easy to understand .

  • @MrBenderNr15
    @MrBenderNr15 5 ปีที่แล้ว

    Why is this guy shouting at me? :,(

    • @bigsursir8515
      @bigsursir8515 3 ปีที่แล้ว

      You were bad and didn't eat your veggies!

  • @weixu6491
    @weixu6491 5 ปีที่แล้ว

    These 2 techniques are awesome

  • @RanjanVron
    @RanjanVron 6 ปีที่แล้ว

    Thank You

  • @MAINMAN8282
    @MAINMAN8282 6 ปีที่แล้ว

    Im a new scrum master and my team hates retrospectives. They will make up fake issues to seem like they are engaged. They all say they dont have any blockers. Help!

    • @rickert1988
      @rickert1988 5 ปีที่แล้ว

      Why they hate retrospectives?

    • @MAINMAN8282
      @MAINMAN8282 5 ปีที่แล้ว

      @@rickert1988 Its a waste of time to give velocity numbers, burndown charts progess to a room full of developers. They dont understand and im trying to show them that this is the teams progress.

    • @Emridas06
      @Emridas06 5 ปีที่แล้ว

      @@MAINMAN8282 Since you say that they feel that the entire retrospective is a waste of time, it seems like you are spending a lot of time on the numbers...Velocity numbers and burndown charts should only be supportive material in a retrospective. You should try and make it more about the team, rather than the project. What does the team feel went well or could be improved on? If you make it about their issues and impediments, and you actively aim to resolve them, they should stop seeing it as a waste of time, as their problems are systematically being resolved.