New Video Channel for Agile Scrum

1 - video vC - ASG - v180301 lowres

Have you seen the new
Video Channel for Agile Scrum? It currently features six videos:


You're invited to check them out.

And for more information on agile/Scrum, including the award-winning book, and to connect:


*****





Award-Winning Book -Agile Scrum

Scenarios: At the End of a Sprint on a Scrum Project, Which is Better, A or B?

A OR B - ASG - v171204 (FOR BLOG) 2


Take a look at the results at the end of a sprint on a Scrum project. There are two scenarios. Both have the same user stories with the same story points for each:

  • User story 1: 13 story points
  • User story 2: 8 story points
  • User story 3: 3 story points
  • User story 4: 5 story points
  • User story 5: 1 story point
  • User story 6: 3 story points
  • User story 7: 1 story point

Scenario A

A OR B (A) - ASG - v171204 lowerres

Here are some details on A:

  • User story 1: 70 hours of work performed, 5 hours of work remaining
  • User story 2: 51 hours of work performed, no work remaining (and it meets the Definition of Done [DoD])
  • User story 3: 45 hours of work performed, 13 hours of work remaining
  • User story 4: 29 hours of work performed, no work remaining (and it meets the DoD)
  • User story 5: 3 hours of work performed, 2 hours of work remaining
  • User story 6: 30 hours of work performed, 17 hours of work remaining
  • User story 7: 4 hours of work performed, 1 hour of work remaining

A is summarized as:

  • 232 hours of work was performed, and 38 hours of work remains
  • 2 user stories were done, and 5 user stories were not completed

Scenario B

A OR B (B) - ASG - v171204 lowerres

Here are some details on B:

  • User story 1: 75 hours of work performed, no work remaining (and it meets the DoD)
  • User story 2: 51 hours of work performed, no work remaining (and it meets the DoD)
  • User story 3: 58 hours of work performed, no work remaining (and it meets the DoD)
  • User story 4: 29 hours of work performed, no work remaining (and it meets the DoD)
  • User story 5: 5 hours of work performed, no work remaining (and it meets the DoD)
  • User story 6: 14 hours of work performed, 33 hours of work remaining
  • User story 5: no work performed, and five hours of work remaining

B is summarized as:

  • 232 hours of work was performed, and 38 hours of work remains
  • 5 user stories were done, and 2 user stories were not completed

What Counts

A OR B (CONCLUSION) - ASG - v171204 LOWERRES

Scrum requires teams to build an increment of functionality during every sprint. Only work meeting the Definition of Done (DoD) is counted as complete, demonstrated at the sprint review meeting, and is potentially shippable.

There were two scenarios. Both had the same user stories with the same story points for each, and the same amount of work hours performed. Yet the outcomes were dramatically different. In A, 2 user stories were done--and are to be demonstrated at the sprint review meeting, and are potentially shippable. In B, 5 user stories were done--and are to be demonstrated at the sprint review meeting, and are potentially shippable. B is the better scenario.

A possible explanation for the differences between the two situations is that the Scrum team in B may have done a better job of limiting Work in Progress.

To learn more about agile/Scrum, check out the award-winning book, Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions. You're invited to visit the digital press kit, watch the trailer, and pick up a copy of the publication—it’s available in paperback and ebook—at Amazon.

*****






Award-Winning Book -Agile Scrum

Are Agile and Scrum Limited to Technology Projects or Technology Industries?

1 - twitter - tech non-tech both - v180331B lowerres

Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive. Traditional development and delivery frameworks are often ineffective. In contrast, Scrum is a value-driven agile approach which incorporates adjustments based on regular and repeated customer and stakeholder feedback. And Scrum's built-in rapid response to change leads to substantial benefits such as fast time-to-market, higher satisfaction, and continuous improvement—which supports innovation and drives competitive advantage.

Agile and Scrum were once the sole domain of software development. However, the benefits and results have not gone unnoticed by others. Practices are being adopted by additional departments and industries. Examples follow.

  • The State of Scrum Report(1) revealed that 21% of Scrum projects are run by departments outside of Technology such as Marketing, Finance, and Sales.
  • An article published in The New York Times(2) noted agile's use in diverse industries—with examples ranging from a museum in Sydney, Australia, to an automobile dealership in Maine.
  • A business brief(3) illustrated how varied businesses—including John Deere, NPR, and Mission Bell Winery—employed agile.

In summary, agile and Scrum are used broadly. For more information on agile/Scrum, pick up a copy of the award-winning book,
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions. For more information on the publication, and to connect:


References:

(1) Scrum Alliance (2017). The State of Scrum Report. Westminster, CO: Scrum Alliance, Inc.
(2) Hardy, Q. (2016, November 25). "The New Workplace is Agile, and Nonstop. Can You Keep Up?" The New York Times, page B1.
(3) Rigby, D. K., Berez, S., Caimi, G., and Noble, A. (2016).
Bain Brief: Agile Innovation. Boston, MA: Bain & Company.

*****






Award-Winning Book -Agile Scrum

Produce Planning Cards™ Help Agile Teams Estimate Work

Exceptional PPM and PMO Solutions™ introduced Produce Planning Cards™ to help agile teams estimate work. An overview of the tool and the technique is provided in a video presented by Agile Scrum and Exceptional PPM and PMO Solutions™. It's available at https://vimeo.com/261680776, and it can be played below.

Produce Planning Cards™ Help Agile Teams Estimate Work from Scott Graffius on Vimeo.


For more information on the Produce Planning Cards™, visit
http://exceptional-pmo.com/Produce-Planning-Cards.

*****

You're invited to connect via social to receive the latest news, tips and more on the professional practice of Scrum—and information on the award-winning book, Agile Scrum. Like us on Facebook and follow us on Twitter.





Award-Winning Book -Agile Scrum