<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Management - Tag - MC Squared</title><link>https://mc-squared.dev/tags/management/</link><description>Management - Tag - MC Squared</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Wed, 05 Aug 2020 09:00:00 +1200</lastBuildDate><atom:link href="https://mc-squared.dev/tags/management/" rel="self" type="application/rss+xml"/><item><title>Sprints, Spikes, and Warm Downs</title><link>https://mc-squared.dev/2020/08/sprints-spikes-warm-downs/</link><pubDate>Wed, 05 Aug 2020 09:00:00 +1200</pubDate><author>Jonathan Miles</author><guid>https://mc-squared.dev/2020/08/sprints-spikes-warm-downs/</guid><description><![CDATA[<h2 id="sprints">Sprints</h2>
<p>My first &ldquo;real&rdquo; day job as a software developer was for a large and well-established company. When I started the software teams followed the Scrum form of Agile.</p>
<p>I strongly dislike some of the terminology used in Scrum, the two main offenders are &ldquo;velocity&rdquo; and &ldquo;sprint&rdquo;.</p>
<p>Poor naming aside, the general approach to software work in Scrum, and many other capital-A Agile methodologies, is to treat the work as a never-ending stream of tickets to be completed over time.</p>]]></description></item></channel></rss>