Agile teams are at their best when the team has a culture of collaboration. One of the most important relationships is between Product Owners and Software Developers.
Having clear goals is critical for maximizing value
The final event in the Sprint cycle is the Sprint Retrospective meeting. The purpose of this meeting is for the team to reflect on and inspect all aspects of the last sprint and create a plan for improving during the next sprint. From communication and relationships, to processes and tools, any topic that impacted the team is up for inspection and consideration. Effective retrospectives can have a massive influence on the velocity of a team over the course of a project - but how do you make sure your retrospective meetings are effective?
The fourth Scrum Event is the Sprint Review meeting. Review meetings are time-boxed and are meant to be a platform for the team to demonstrate working software to the stakeholders and receive feedback. I reached out to our team to get their guidance on how to have a successful and valuable sprint review.
During the course of a sprint there is a Product Backlog Refinement meeting. The scrum team and Product Owner should discuss how much refinement is needed to ensure the backlog is about 1-2 sprints refined out and the team has enough work to pull into sprint if they needed to.
Backlog Refinement meetings are meant to further prepare and curate upcoming backlog items for the next sprint. This high-level description of “Refinement” can mean a lot of different things. I reached out to our team to get their perspectives on what value backlog refinement provides to the team.
During the course of a sprint there is a daily meeting called the Daily Scrum. This meeting is normally held in the same location and at the same time each day, morning being the most preferred. This allows the team to know what all of the team is working on for the day and if they are running into any issues.
The second event during an Agile Sprint is the Daily Scrum. The daily scrum (sometimes colloquially called the 'standup' meeting) is a recurring, 15-minute meeting that is held by the team and is for the team. The sole reason for having this meeting every day is to empower the team to be successful.
Sprint Planning is the first event of the sprint, where the development team prepares for the couple of weeks ahead. Here we explain the sprint review in terms of the 5 key questions - who, what, where, when, and why. Then we’ll dive into some common issues and anti-patterns we’ve seen in the industry.
The by-the-book purpose of Sprint Planning is for the Product Owner to describe the highest priority features to the team and give the rest of the Development Team a forum to ask questions. The team should come out of the planning meeting with a sprint goal and a sprint backlog. While these two items are very tangible, I have found many other valuable takeaways from sprint planning meetings.
When a peer does something great there are many ways to acknowledge their behavior
What does self-organization mean, what are the fears an organization has regarding self-organizing teams and why are self-organizing teams so important? Erin shares some thoughts these and other questions.
Typically we are showing our development teams and stakeholders the final designs and nothing about HOW that design came to be and it is met with skepticism. Is it possible to get automatic design buy-in from your development team?
Thinking at the next higher level can extend to thinking at any other role.
We asked our experts to help illuminate some of the bad habits that someone new to this role might encounter.
I recently re-read Mindset by Carol Dweck for a book club. In it the author is talking about the mindset of a student when they had received a heavily critiqued research journal they had submitted for publication and was ‘stuck in a rut’.
Are we as software professionals guided by a set of ethical standards?
For those not aware, the Association for Computing Machinery is currently revising their Code of Ethics.
Proving the ideas of pair programming, producing software in increments, reviewing shippable software and adapting quickly to customer feedback came from making cookies.
One of the most critical aspects of any agile process is the inspection/adaptation cycle.
Every major project experiences some level of failure. Eventually yours will too, and that’s ok! Failure is direct and actionable feedback that creates the opportunity to adjust.
More and more people today find themselves working remotely and struggling to stay connected.
Stress helps the brain and body respond to daily challenges, but when experienced over prolonged periods it can snowball into Burnout.
The Sprint Review is a critical part of the Scrum framework. It's a time to stop and inspect the product, gather feedback, and engage in discussion.
Growing your organization’s agility can seem like casting a movie or building a sports team with the various roles/positions to fill -- Product Owners...
We have all suddenly found ourselves physically separated from our teams, yet the need to collaborate still exists.