9 Best Practices for Your Daily Scrum Meeting

Project Bliss

When my team first started holding a daily scrum meeting, it honestly felt awkward. From the lessons I’ve learned through experience, I’ve compiled nine best practices that have helped our daily scrum meetings stay focused and efficient. The Purpose of the Daily Scrum Meeting.

SCRUM 263

Difference Between Agile Project Management and Scrum

Brad Egeland

Scrum is also the framework of agile for completing complex projects. The scrum master is a facilitator of an agile team. Many organizations take CSM training and certifying their skills in practicing Scrum. This page is a comparison between Agile and Scrum and outlines the main difference between them. Scrum: An iterative software model that follows a set of roles, responsibilities, and meetings that do not change with time. What is Scrum?

SCRUM 180

Scrum or Kanban for Application Support teams?

Digite

The questioner asked – “I have recently joined a company and to one of the projects that I’m engaged we have this Scrum team that has a mixed backlog (USs and Bugs). Frequently, especially in a Scrum environment, it can be difficult to match the cadence of doing both.

SCRUM 65

Kanban and Scrum Together – Not So Fast

Digite

Continuing our theme of facilitating Scrum and Kanban, we’re honored to publish another guest blog post by Dave White on ‘Kanban and Scrum Together – Not So Fast’. Here Dave white has shared his thoughts on the article ‘Kanban and Scrum Together’ written by Steve Porter. KANBAN AND SCRUM TOGETHER – NOT SO FAST. A colleague of mine who works at Scrum.org now posted a blog about how Kanban and Scrum are stronger together.

SCRUM 40

The Difference Between The Kanban Method and Scrum

Digite

In this article, he outlines the similarities of the two as WIP Limiting, Pull-based systems – with cadences and a focus on learning – while also explaining their differences. A question that I often get while speaking with people is: What is the difference between Kanban and Scrum? Scrum. Scrum is primarily influenced by the Agile Manifesto which describes the “Agile” value system. Cadences. Many Kanban teams have a Queue replenishment cadences.

A Review Of Scrum For Kanban Teams

Digite

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods. And maybe that isn’t how Scrum is taught.

SCRUM 40

A Comprehensive Guide to Agile Project Management

Redbooth

Borrowing from Scrum methodology, an agile team has three main roles : Product Owner : An executive or key stakeholder who leads the project with vision. Scrum Master : The player-coach most akin to a project manager who oversees operations and guards the process.

Agile 137

Is SAFe Agile?

Digite

Since the arrival of Scaled Agile Framework in the world market, there have been comparisons ad nauseum between the Scrum and SAFe frameworks. This is a key tenet of SAFe framework and referred to as ‘Develop in Cadence’ in the big picture.

Agile 52

While collocation is nice-to-have, meeting in person should be mandatory!

Kiron Bondale

Having such teams distributed geographically should not be an issue so long as there is still the opportunity to conduct ceremonies such as a Scrum of Scrums to manage interdependencies, maintain alignment in release cadence and to raise shared impediments to the right level of resolution.

2017 156

Kanban = Continuous Delivery? Not Necessarily

Digite

We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established. Lean/ Kanban agile Kanban Lean Lean Software Development Management Release Management Scrum

Team using “Waiting for Release” column on their kanban board

Digite

We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. Lean/ Kanban agile Kanban Lean Lean Software Development Management Release Management ScrumHere’s is another question that I recently answered on a discussion forum –. “My My team is using Kanban board but they seem to prefer to collate a couple of tickets then ‘do a release’ as appose to releasing each ticket.

Releases and Deadlines in Agile

Herding Cats

This is not to say those 5 developers sitting around the table with the Product Owner and the Scrum Master are not working on vitally important code. Cadence Release - when a fixed period ends, go with what is ready to go. Cadence Release paradigm, is a flow-based approach.

Handling Unplanned Work

Leading Agile

Scrum calls the list the Product Backlog.) Fortunately, contemporary lightweight software delivery methods based on time-boxed iterations (like Scrum) or continuous flow (like Kanban) include mechanisms to handle unplanned work gracefully.

2018 72

Essential SAFe 4.0 – How is it Different from SAFe 4.0?

Digite

Release Train and Cadence. Without an Agile Release Train, it would be impossible to have multiple teams delivering in Cadence, with synchronized sprint start and end dates. An RTE is to a Train (ART) what a Scrum Master is to a Sprint. Essential SAFe 4.0

Beginner’s Guide to Kanban for Agile Marketing

Digite

Compared to Scrum, Kanban is a young work-management method. But, for teams that chafe under the strictures of the Scrum process, Kanban can be a freeing alternative. In fact, many Scrum teams use this type of visualization to manage their work.

SCRUM 52

Agile Release Train (ART)

Digite

Program Increments (PIs) provide a development timebox (default 10 weeks) that uses cadence and synchronization to facilitate planning, limiting WIP, provide for aggregation of value and assure consistent retrospectives.

Agile 72

Unravelling PI Planning

Digite

As the PI has 5 iterations with multiple teams working in cadence to achieve a common vision, it is important for these teams to assemble and plan out the course of action for the entire PI duration. Product Owner and Scrum Masters – to enable Team breakouts and Feature to Story decomposition.