Tag Archives: system

The Rules of Scrum: I know my product well and can quickly describe its high-level architecture

All Scrum Team Members, including the ScrumMaster and Product Owner, should understand the high-level technical aspects of the product that is being built.  As well, that understanding should be solid enough, that it can be communicated to other people.  This understanding helps the team members in many situations dealing with each other and with stakeholders.  Understanding the structure of the system is an aspect of Transparency.  This is essential for maintaining overall quality of the product. Development in one part of the product or system should never cause problems for any other part of the product or system.  If team members do not know their product in this way, it can cause significant problems in communication and in how Product Backlog Items are implemented.


Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

Please share!
Facebooktwittergoogle_plusredditpinterestlinkedinmailFacebooktwittergoogle_plusredditpinterestlinkedinmail

The Rules of Scrum: PBIs are “slices” through our system (features or functions)

All PBIs completed by the team should be “potentially shippable” increments of complete value.  In order to do this, they must touch all the layers and components of the product so that the functionality produced is truly complete, not just a prototype… a “slice” through the system.  In other words, all of the work that is required for shipping product needs to be completed on all individual PBIs.  Creating slices through our system allows the Scrum team to deliver value each and every Sprint and also allows for the Product Owner to change direction to a new feature if it is more valuable for a future Sprint.  What happens if we don’t create and complete PBIs that are slices through the system?  We risk falling into a pattern of not having a potentially shippable product each Sprint, and, even worse, we may regress into a waterfall type process that produces nothing of value to the customer until the end of the project.


Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

Please share!
Facebooktwittergoogle_plusredditpinterestlinkedinmailFacebooktwittergoogle_plusredditpinterestlinkedinmail

The Rules of Scrum: All PBIs are related to a single product (or system)

Scrum Teams work on one product at a time.  The Product Backlog represents all of the work that needs to be done on that single product.  The complete list of Product Backlog Items represents the goal of delivering all of the presently known features of a product.  Multiple teams working on a single product, therefore, work from a single, shared Product Backlog.  Working on Product Backlog Items from multiple Products causes the team to task switch into a different business domain and possibly into a different technical domain.  Task switching creates wasted mental effort and therefore causes a team to be less effective than they could otherwise be.  Having a single product to work on creates focus in both the business and technical domains.


Affiliated Promotions:

Try our automated online Scrum coach: Scrum Insight - free scores and basic advice, upgrade to get in-depth insight for your team. It takes between 8 and 11 minutes for each team member to fill in the survey, and your results are available immediately. Try it in your next retrospective.

Please share!
Facebooktwittergoogle_plusredditpinterestlinkedinmailFacebooktwittergoogle_plusredditpinterestlinkedinmail
Berteig
Upcoming Courses
View Full Course Schedule
Certified ScrumMaster® (CSM)
Toronto
C$1595.00
Oct 22
2019
Details
Kanban System Design® (KMP I)
Toronto
C$1795.00
Oct 24
2019
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1599.00
Oct 25
2019
Details
Team Kanban Practitioner® (TKP)
Toronto
C$1195.00
Oct 28
2019
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1599.00
Nov 1
2019
Details
Certified ScrumMaster® (CSM)
Toronto
C$1595.00
Nov 6
2019
Details
Certified ScrumMaster® (CSM)
Toronto
C$1355.75
Nov 19
2019
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Nov 22
2019
Details
Certified ScrumMaster® (CSM)
London
C$1525.75
Nov 22
2019
Details
Certified Scrum Professional - ScrumMaster® (CSPSM)
Online
C$1869.15
Nov 22
2019
Details
Professional Scrum Master® (PSM I) [PSF Courseware]
London
C$1495.00
Nov 25
2019
Details
Certified Scrum Product Owner® (CSPO)
Toronto
C$1525.75
Nov 26
2019
Details
Licensed Scrum Master® (LSM)
Toronto
C$1355.75
Nov 27
2019
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Nov 29
2019
Details
Certified ScrumMaster® (CSM)
Toronto
C$1355.75
Dec 3
2019
Details
Kanban Management Professional® (KMP II)
Toronto
C$1525.75
Dec 5
2019
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Dec 6
2019
Details
Team Kanban Practitioner® (TKP)
Toronto
C$1015.75
Dec 10
2019
Details
Professional Scrum Master® (PSM I)
Toronto
C$1270.75
Dec 10
2019
Details
Kanban System Design® (KMP I)
Toronto
C$1525.75
Dec 11
2019
Details
Team Kanban Practitioner® (TKP)
Toronto
C$1015.75
Jan 16
2020
Details
Certified ScrumMaster® (CSM)
Toronto
C$1355.75
Jan 21
2020
Details
Certified Scrum Product Owner® (CSPO)
Toronto
C$1525.75
Jan 23
2020
Details
Licensed Scrum Master Product Owner® (LSMPO)
Toronto
C$1695.75
Jan 28
2020
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Feb 1
2020
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Mar 7
2020
Details
Advanced Certified ScrumMaster® (A-CSM)
Online
C$1359.15
Mar 21
2020
Details