{"id":5,"date":"2009-08-08T11:42:40","date_gmt":"2009-08-08T11:42:40","guid":{"rendered":"http:\/\/ericlaramee.com\/blogit\/?p=5"},"modified":"2009-08-08T11:42:40","modified_gmt":"2009-08-08T11:42:40","slug":"scrum-is-like-an-onion","status":"publish","type":"post","link":"https:\/\/agilepartnership.com\/fr\/scrum-is-like-an-onion\/","title":{"rendered":"Scrum is like an onion…"},"content":{"rendered":"

\"\"<\/a>Scrum stinks? I don’t think so.
\nScrum makes you cry? I’ve seen it happen.
\nYou leave Scrum out in the sun, it gets all brown, start sprouting’ little white hairs?
\nNo! Layers! Scrum has layers!<\/p>\n

The outer layer of Scrum is the high level process.\u00a0 This includes the ceremonies of Scrum such as the daily scrum, the sprint review and retrospective. We can also include the product and sprint backlogs,\u00a0\u00a0 and burndown charts.\u00a0 These things can be explained in a few minutes to a bunch of drunken friends at a party and they’d still remember it in the morning.<\/p>\n

Going deeper into the next layer involves something that comes before the actual Scrum framework. Before diving into a Scrum project, we need to assemble a cross-functional team and create a common vision with the help of a competent Product Owner\u00a0 and ScrumMaster.\u00a0 A project launch, Sprint 0, or whatever you want to call it is needed to deliver the oh so important Project Charter.\u00a0 Only then can a team slowly move from being a group of individuals working for the same manager to a group of professionals collaborating towards the same goals.<\/p>\n

Our onion also has a technical layer to it.\u00a0 The incremental and iterative development layer required in Scrum implies sound engineering practices.\u00a0 At the top of this list of practices is testing.\u00a0 If the product is not thoroughly tested, disaster will soon ensue.\u00a0 If non-tested code is prevalent in the application, courage to refactor will be low and the end result will be a design dead code base.\u00a0 The team must, at a minimum, be exposed to various practices such as Test-Driven-Development, Domain-Driven-Design and Agile Modeling.\u00a0 The scrum team must deliver a high quality product every 4 weeks that responds to the client’s needs, and Agile engineering practices can help the team achieve just that.<\/p>\n

Moving inwards gets a bit more stinky.\u00a0 It always amazes me how such a simple framework can provoke so much change.\u00a0 Changes are required not only within the the Scrum team but at all levels of the organization and resistance to change is often more prevalent with\u00a0 upper management than any other sector. This is actually quite funny because upper management is the one calling us to \u201cdeliver\u201d Scrum in the organization.<\/p>\n

Scrum has a whole bunch of other layers but those are the first ones that came to mind. Not to mention that my eyes are quickly turning red!<\/p>","protected":false},"excerpt":{"rendered":"

Scrum stinks? I don’t think so. Scrum makes you cry? I’ve seen it happen. You leave Scrum out in the sun, it gets all brown, start sprouting’ little white hairs? No! Layers! Scrum has layers! The outer layer of Scrum is the high level process.\u00a0 This includes the ceremonies of Scrum such as the daily […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[17,18],"tags":[],"class_list":["post-5","post","type-post","status-publish","format-standard","hentry","category-agile","category-scrum"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts\/5","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/comments?post=5"}],"version-history":[{"count":0,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/posts\/5\/revisions"}],"wp:attachment":[{"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/media?parent=5"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/categories?post=5"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilepartnership.com\/fr\/wp-json\/wp\/v2\/tags?post=5"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}