ken.schwaber@verizon.net [SCRUMDEVELOPMENT]
2015-10-05 14:21:30 UTC
ScrumsUP âŠ. Stuff that has happened or Iâve run into that I think you should know about.
Every so often.
Dave West joined me at Scrum.org on October 1. To learn more about Dave, look up https://www.linkedin.com/in/davidjustinwest https://www.linkedin.com/in/davidjustinwest . More important, read about his reasons for joining me at scrum.org http://scrum.org/ in the blog http://blog.scrum.org/why-i-joined-scrum-org/ http://blog.scrum.org/why-i-joined-scrum-org/
Scaled Scrum development is the child of many parents. One the side of caution, we have descaling and scrumbling. On the side of progress, we have common functional and architectural facilities that standardize and accelerate development These facilities are common routines with private capabilities for data access, user interface, communications, queuing, measurement, and other shared capabilities.
The public interface for accessing these facilities should be exposed in an API. The development organization or at least the Nexus Integration Team should develop and deploy a Software Development Kit (SDK) that documents and shows how to use the API.
All of the scaled Scrum teams should use such a SDK. Iâll be teaching this in Boston on November 17-18 with Rich Hundhausen and Rob Maher. Look here http://bit.ly/1VAWzKc#http://bit.ly/1VAWzKc for other Scaled Professional Scrum workshops elsewhere, and sooner.
Scaled Scrum requires quality increments from each team, and an integrated increment from all of the teams. Quite a few people view quality as having passed all of the tests. I recently blogged http://bit.ly/1MaXE6n#http://bit.ly/1MaXE6n about what a quality increment means to me and scaled development.
This is the link we should use for the sign-up form going forward:
http://eepurl.com/bxWfpX
ScrumsUP List http://eepurl.com/bxWfpX
http://eepurl.com/bxWfpX
ScrumsUP List http://eepurl.com/bxWfpX ScrumsUP List Email Forms
View on eepurl.com http://eepurl.com/bxWfpX
Preview by Yahoo
Every so often.
Dave West joined me at Scrum.org on October 1. To learn more about Dave, look up https://www.linkedin.com/in/davidjustinwest https://www.linkedin.com/in/davidjustinwest . More important, read about his reasons for joining me at scrum.org http://scrum.org/ in the blog http://blog.scrum.org/why-i-joined-scrum-org/ http://blog.scrum.org/why-i-joined-scrum-org/
Scaled Scrum development is the child of many parents. One the side of caution, we have descaling and scrumbling. On the side of progress, we have common functional and architectural facilities that standardize and accelerate development These facilities are common routines with private capabilities for data access, user interface, communications, queuing, measurement, and other shared capabilities.
The public interface for accessing these facilities should be exposed in an API. The development organization or at least the Nexus Integration Team should develop and deploy a Software Development Kit (SDK) that documents and shows how to use the API.
All of the scaled Scrum teams should use such a SDK. Iâll be teaching this in Boston on November 17-18 with Rich Hundhausen and Rob Maher. Look here http://bit.ly/1VAWzKc#http://bit.ly/1VAWzKc for other Scaled Professional Scrum workshops elsewhere, and sooner.
Scaled Scrum requires quality increments from each team, and an integrated increment from all of the teams. Quite a few people view quality as having passed all of the tests. I recently blogged http://bit.ly/1MaXE6n#http://bit.ly/1MaXE6n about what a quality increment means to me and scaled development.
This is the link we should use for the sign-up form going forward:
http://eepurl.com/bxWfpX
ScrumsUP List http://eepurl.com/bxWfpX
http://eepurl.com/bxWfpX
ScrumsUP List http://eepurl.com/bxWfpX ScrumsUP List Email Forms
View on eepurl.com http://eepurl.com/bxWfpX
Preview by Yahoo