Agile Project Management with Scrum right now? Understanding Scrum is easy, but implementing it is hard. The Scrum Framework contains 3 artifacts (Product Backlog, Sprint Backlog & Increment), 5 events (Sprint, Sprint Planning, Daily Scrum, Sprint Review & Retrospective) and 3 roles (Product Owner, Scrum Master & Development Team). Many organisations start with the artifacts and events, but do not have enough focus on implementing the roles (typically Scrum Master and Product Owner) as they are intended. The result is often an implementation of Scrum, where all events & artifacts are present, but Scrum doesn’t really come to life. As a leader you should have focus on helping the roles Scrum grow. Once the people understand their role, they can take responsibility for the events & artifacts.
They created two work streams. Each with team members from different departments. This has allowed the conversations about a project to always happen as a team and in this way things began to become more apparent and transparent. “What we found was that we need to use plain English in everything that we communicate. Not only amongst our team, but also with our clients,” said Brett when speaking about the needed tweaks to the agile terminology and language when it was introduced in 2015. Using plain English and providing definitions up front for necessary acronyms are crucial to have mutual understanding within your team and with your customers.
When looking to create any learning culture, including an agile learning culture, leaders need to be on board and help create a vision. A Human Capital Institute survey from 2015 found that 74% of companies wanted to create a learning culture. Those who succeeded at doing that did so by incorporated learning, growth, challenge, agility, risk-taking, and mistake-making as a positive aspect of the culture they envisioned. This vision and these qualities need to be incorporated into how the company communicates and interacts with outside organizations, employees, and potential employees. Agile learning needs to have a place in all areas of the organization and at all levels of the organization. See more details on Certified Product Owner course.
One of the hardest parts to maintain with Agile Project development is the Daily Scrum. Essentially, Daily Scrum meetings are daily sessions where the development team members organize themselves to get things done for the day and to review what happened yesterday. It’s for the team to know where they are in the sprint, to discuss the tasks and User Stories and for the Scrum Master to identify what obstacles have to be taken out of the way. It is usually best to organize it in the morning when it suits everyone. However, when working with remote teams with time differences, an afternoon Daily Scrum might be best appropriate. But just like any part of the Agile Development methodology, the Daily Scrum can deteriorate and turn messy. Here are ways to make the most out of Daily Scrum meetings and avoid its misuse.
Retrospective (also called “retro”) is the core element of Scrum, so it must be held appropriately. Retrospective isn’t just a fancy word. It’s a technique that has its rules. Many Scrum teams turn sprint retrospectives into a meaningless waste of time because they don’t stick to the rules. Remember that a sprint retrospective gives a Scrum team a chance to improve their workflow. For a typical month-long sprint, a retro should take no more than 3 hours. Spending more time on it is inefficient and counterproductive. During a sprint retrospective, team members should do the following: Share their ideas about a just-finished sprint (process, relationships, environment); Decide what went well and what went wrong; Offer improvements and propose a plan for implementing them. As a result, your team will define problems and suggest solutions. Don’t forget that sprint retrospectives require the presence of a Scrum Master who moderates the event and encourages the team. Sprint retrospectives help Scrum teams become more efficient and professional. Read additional details at this website.