{"id":1638,"date":"2016-07-26T14:15:27","date_gmt":"2016-07-26T21:15:27","guid":{"rendered":"http:\/\/10kdev.net\/?p=1638"},"modified":"2017-11-12T09:59:17","modified_gmt":"2017-11-12T16:59:17","slug":"agile-ceremonies","status":"publish","type":"post","link":"http:\/\/10kdev.net\/?p=1638","title":{"rendered":"Agile . . . Ceremonies"},"content":{"rendered":"
\"Ceremony\"<\/a>

After the Agile Ceremony there will be sheet cake and Diet Coke!
And . . . your macaroni art is due Tuesday.<\/p><\/div>\n

Ceremony?<\/span><\/p>\n

Yes ceremony. \u00a0I really hate it when that term is used, it implies that an agile meeting is of a level of importance equal to the big things in life. \u00a0NO IT IS NOT. \u00a0This is just code.<\/p>\n

This definition is\u00a0from Atlassian<\/a>:<\/p>\n

Meetings, or “ceremonies” are an important part of agile development. But they are one of many important elements, and shouldn\u2019t be conducted in a vacuum. (It’s tempting to add some ceremonies to a waterfall project and call it “agile”, but this will get you nowhere.)<\/em><\/p>\n

Let’s take a look at each of the agile ceremonies, and understand how they empower the team and drive agile development.<\/em><\/p>\n

Note: A number of these ceremonies come from the practice of scrum which is an iterative, time-boxed approach to implementing agile. The concepts behind these ceremonies can be applied to other forms of agile like kanban or lean. “Sprint” is a scrum-specific term. Other forms of agile use the more generic term “iteration” to indicate a time-boxed period of development.<\/em><\/p>\n

That’s one definition.<\/p>\n


\nI find the use of the term offensive.<\/strong>\u00a0 Can I be offended? \u00a0Yes.<\/p>\n