Lead Agile Meetings: Productive,Effective,Efficient Meetings
Many new agile teams think flexibility in their meetings allows them to do whatever feels right. In reality, agile projects move more smoothly by running short, well-structured activities. Each activity is time boxed, so the teams stay on track and work within a set time and agenda.
In this course, agile expert Luke Angel outlines how to make agile meetings as productive as possible. He provides guidance on common activities such as release planning, daily stand-ups, sprint planning, retrospectives, and product demos. Throughout the course,you will learn about common meeting pitfalls and the challenges of keeping activities on track.
An Agile project has less upfront planning. When you start an Agile project, you don’t know what the completed vvvvproduct will look like. You start with a general notion of where you’re going and you make frequent improvements v how to get there. Agile is adaptive, not predictive. Much of the energy comes from new ideas and changes. In this course we’ll take a deeper dive into some of the Agile ceremonies. We’ll go further into the planning meetings and talk about
Whether your a Project Manager, a Software Developer, or a Senior Manager, this course is designed to help you get greater agility from your team. So let’s get started, Driving Productive Agile Meetings.
In this course you will learn
- How to Run Agile Meetings
- How to Keep Meetings Lightweight
- How to timebox to avoid meetings that run on forever.
- How to create a release schedule
- Delivering without scope
- Inviting the right groups
- Hosting awesome daily stand ups
- Break through roadblocks
- Avoiding common pitfalls
An Agile project has less upfront planning. When you start an Agile project, you don't know what the completed product will look like. You start with a general notion of where you're going and you make frequent improvements on how to get there. Agile is adaptive, not predictive. Much of the energy comes from new ideas and changes. In this course we'll take a deeper dive into some of the Agile ceremonies. We'll go further into the planning meetings and talk about how to run a disciplined agenda. This series is designed to help your team increase the pace and quality of their work. If you're new to Agile or not familiar with some of the terms, then you may want to watch the series from the very beginning. So let's get started, Driving Productive Agile Meetings."
Agile Meetings: Form and Function
Many Agile teams call their meetings scrum activities. These activities are well structured and scheduled. They're also baked into team's overhead. The scrum activities shouldn't be confused with the spontaneous chatter that's part of a shared workspace. In this section you will learn how to keep theses meeting lightweight and on point
Many Agile teams call their meetings scrum activities. These activities are well structured and scheduled. They're also baked into team's overhead. The scrum activities shouldn't be confused with the spontaneous chatter that's part of a shared workspace. These impromptu meetings are what the developers need to sort out problems and hammer out details. The shared workspace heavily relies on osmotic communication. Osmotic communication is similar to dinner party chatter. In this section she will learn how to effectively run these meetings.
In this section we are going to build sprints with timeboxes The timebox is the building block on which all agile planning and scheduling depends. All the work in an agile project is broken down into smaller timeboxes, Even the developers have their own timebox, they must work within their eight hour day, any overtime will interfere with the predictability of the delivery. By The end of the section you will understand the importance of a timebox.
Quiz on Agile Meetings
Scheduling a release date might seem counter to agile's ability to make frequent changes. The product owner prioritizes the work every sprint. If the product owner can't define the deliverable, then how can they schedule a release date? This section will define how to do this and more.
In traditional projects, the scope is the what and how of your product. It's the constraint that keeps you from over delivering. Agile projects don't start with a finished product's scope. In the section we will go over how to deal with this and more.
The Scrum Master is responsible for setting up efficient activities, and they need to be very careful about who contributes. Think about the long-term efficiency: they need to make sure that the right people are talking and the right people are listening. In the section we review how to fines your way to meeting success.
Its a Quiz
Developing and Maintaining Team Cohesion
Of all the Agile activities, the Daily Standup is probably the most misunderstood. The standup is about self-organizing. The development team stands in a circle and updates each other about what they're working on. It sounds simple enough, but that's not how most organizations operate. Most meetings are driven by whoever called the meeting. A standup is contrary to how most people think about working. In this section you will learn how to run the standups to product the best possible results.
The first group of obstacles is setting up the team. So S for setup. In some
organizations, setting up a shared work space is an enormous obstacle. If your
agile team works on a floor with rows of cubicles, then it may be difficult to
create a shared work space. If the organization thought this was the best way
to work, they wouldn't create cube farms. in this section we will go over how
to work though these situations and move forward.
Assembling Your Sprints
Sprint planning is a crucial part of the team's predictability and transparency. It's when the team decides what they need to deliver for that sprint. The activity is usually timeboxed to two hours. The product owner will take the top value user stories and present them to the developers. Then they'll have the team task out these stories.
To become fully agile, the team needs to abandon much of their traditional project management mindset. Traditional project management can be high stakes. If you're wrong about an estimate, there can be dangerous consequences. An Agile team is different. An Agile team needs to accept a degree of uncertainty and move forward anyway.
Sprint Demonstrations: Showing The Teams Work
At the end of a Sprint, the team schedules a review of the product. The team will show everything they've accomplished in the last two weeks. This is sometimes called the Sprint Review. It's also commonly called the Demo. It's a double-edged sword to call this activity a demo. On the one hand, you're much more likely to get everyone to attend. A demo sounds far more alluring than a review.
In agile, there isn't as much upfront planning. Instead, the team relies on real-time feedback to keep the project on track. These feedback loops are the best way to respond to changes. That's why agile gets real value from these feedback loops. It's the engine that drives the team to produce and improve. The five scrum activities are designed to create these loops. The daily standup, product backlog, demo, and retrospective, are all working to create a feedback loop for the team.
Understanding and Avoiding Problems
Everyone has an essential role to play in an Agile team. They need to know when it's their turn to participate, speak up or just listen. Part of creating good feedback loops is keeping the team listening and not overwhelmed with outside interference. There's an old joke about Agile. It starts out with a pig and a chicken. The pig and the chicken decide to start up a small restaurant. They sit together in their empty restaurant and think about what to put on the menu. The pig asked the chicken, "What do you think we should serve for breakfast?" The chicken responds, "Well, what about bacon and eggs?" Then the pig says, "Wow, if we serve that, you'd be interested "but I'd be committed." You should think about this joke when you start thinking about your Agile team.
There are a lot of challenges around having a good daily standup. Often managers could hijack your activity. Your organization's chickens may see this as a team progress meeting. They'll take up valuable time with questions and visioning. All these obstacles are there. If you're the scrum master, you should be aware of them. But the team has its own set of challenges. Even without all these outside distractions, it's difficult for the development team to get into a daily rhythm. There are usually many different personalities on a development team. But there are some characteristics that may cause problems. You'll likely see these problems and best practices to solver them in this section.
Breaking the sprint is when the team cannot deliver at their commitments at the end of the two weeks. This is sometimes called abnormally terminating. If there are old-school developers, you might hear the term abnormal ending or abandoning the sprint. Some teams call it blowing up the sprint. Whatever you call it, the result is usually the same.
If you were starting work at 9:00 AM and had three hour-long tasks, how would you organize your morning? When most people are asked this question, they say that they would start one task at 9:00 AM, begin another at 10:00 AM, and finish the last one before noon. They would start one task at a time, each one finishing before the next one began. In reality, not many people actually work that way. The way most people work is they start all three at 9:00 AM, and do a little bit of each simultaneously. They figure that way, they'll have more time for all three. If something takes longer, they'll still have more time before noon. This is commonly called multitasking.
The _______ Role Is To Protect The Team and Their Work.
While we recognize that there are allot of creative, non-repetitive, variable work in agile development projects, many work items, ceremonies, and activities can benefit from systematic, reproducible and standardized tasks test and options that can be captured in customizable checklists prepared and used by empowered agile teams.