MINNEAPOLIS – October 4, 2018 – Collaborative Leadership Team (CoLead Team), an industry leader in providing Scrum and Agile coaching and training, hosted its sixth annual Scrum Day Minnesota on October 4, 2018 at the University of Minnesota – St. Paul campus. The sold-out not-for-profit event brought together more than 300 individuals from around the region to share their stories and network as a community.
Collaborative Leadership Team Among First to Achieve Scrum@Scale Training Certification
Scrum@Scale® training session scheduled for October25-26 in Minneapolis
MINNEAPOLIS – September 28, 2018 – Collaborative Leadership Team (CoLead Team), an industry leader in providing Scrum and Agile coaching and training, has announced it is now certified for leading Scrum Inc’s Scrum@Scale™ (S@S) curriculum. One of the first and only organizations certified to lead S@S training, CoLead Team has two certified S@S trainers on staff and will be hosting at S@S session on October 25-26, 2018 in Minneapolis. The upcoming session will be led by Dee Rhoda, CSP®, ICP-ACC®, CLP, Scrum at Scale Trainer®.
In a recent Certified ScrumMaster (CSM) course, a student new to Scrum was a bit confused by the repeated reference to the ScrumMaster as a “coach”. “What do you mean coaching or when does this coaching happen?” was the question raised.
MINNEAPOLIS (September 10, 2018) – Collaborative Leadership Team (CoLead Team), an industry leader in providing Scrum and Agile coaching and training, is proud to announce that two of its team members have earned the rigorous Path to CSP Educator℠ credentials enabling them to deliver the Advanced Certified Scrum Master (A-CSM℠) certification. CoLead Team Founder and CEO, Angela Johnson and Certified Scrum Trainer, Christian Antoine are two of the first group of ten individuals to achieve this certification in the United States.
So just what is a product backlog item in the Scrum framework? One of the Scrum artifacts is the Product Backlog. A Product Backlog Item, or PBI, is similar to the intent of the user story. It was a place to note conversations that needed to be held with the Product Owner and anyone else necessary to flush out more information about the item. As conversations are held, results of those conversations can be added to the PBI in plain old words. No prescription necessary!