<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Edward Sumerfield on Medium]]></title>
        <description><![CDATA[Stories by Edward Sumerfield on Medium]]></description>
        <link>https://medium.com/@esumerfield?source=rss-ada48a0ba7d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*82zvg6yzN8CHlSA3.jpg</url>
            <title>Stories by Edward Sumerfield on Medium</title>
            <link>https://medium.com/@esumerfield?source=rss-ada48a0ba7d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:28:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@esumerfield/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Our Agile Looks Like]]></title>
            <link>https://medium.com/@esumerfield/what-our-agile-looks-like-bf81aa656047?source=rss-ada48a0ba7d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf81aa656047</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Edward Sumerfield]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 00:06:26 GMT</pubDate>
            <atom:updated>2018-04-24T00:06:26.626Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Seven years with the same Agile team.</blockquote><p>I want to try to describe what Agile feels like on a team that is willing and committed to be the best it can be. From 7 years ago learning Scrum, adapting Scrum, switching to a Kanban approach and back to Scrum, this team has evolved together as one cooperative group. Some enjoy the executive and some the programming roles but all of us love being excellent at what we do.</p><h3>A Week</h3><p>We usually run a 1 week sprint with only a couple of periods where we ran for two weeks but those didn’t last long. The basics of what we do are the same as most Agile teams with a couple of exceptions that address Whole Company Agile and Dev-ops.</p><ul><li>Monthly executive meetings to define and adapt organizational goals to maintain road-maps.</li><li>Weekly Road-map Planning for Product Owners and development leads to prepare work for the future (1 hour).</li><li>Weekly Sprint Review for everyone to verify our work plan is up to date (15 minutes).</li><li>Retrospective for everyone to share (30 minutes to 1 hour).</li><li>Sprint Planning to review the Stories lined up for the next sprint (1 hour).</li><li>Team planning to allow teams to drill down and define how they will approach implementing the Stories (30 minutes).</li><li>Daily Stand-ups for everyone (5–30 people, see “Tribe Level Ceremonies”) that focus on “you need to know” and “things are looking good” (15 minutes).</li><li>Daily Environment Reviews for everyone to review key metrics of the production systems (15 minutes).</li></ul><p>For the development teams these ceremonies take 30 minutes each morning and planning day takes up the morning. We try to keep all non-programming activities on one day, usually a sprint boundary.</p><p>Executives and Product Owners take additional time as needed depending on the complexity of the pending work.</p><h3>Ceremonies</h3><p>Agile speaks of these ceremonies in terms of the goals they intend, but there is a lot more going on here. Everyone is accountable for their own contributions. Everyone is holding others accountable for their contributions. Everyone is supporting each other to achieve the shared goal.</p><p>To get to this point the team members need to be open to fail and willing to change to succeed. This drives humility and commitment in each other through the shared responsibility.</p><h3>Dev-Ops</h3><p>We have evolved our understanding and approach to dev-ops for years. We are still not happy with all aspects of this problem, especially in strict PCI environments.</p><p>Early problems included:</p><ul><li>Ops only on call schedules.</li><li>Location isolation.</li><li>Isolated ceremonies.</li><li>Fundamental skill differences prevented conversation and collaboration.</li></ul><p>This is a complete article on its own but we arrived at this mix of changes:</p><ul><li>All teams include infrastructure skilled individuals which has forced developers to cross train on the impact their code has.</li><li>Teams with a more infrastructure workload also included programmers which forced cross training and encourages automation from a developers focus, with source control, CI etc.</li><li>Delivery teams own responsibility for the infrastructure their code will use which has forced investment in automating.</li><li>Each team owns the on-call schedules for their products and responds to production incidents when called. This forces delivery teams to optimize those alerts and stay no top of run-time quality.</li><li>Automation-first ensures we own the modeling of deployment configuration along side product configuration which radically improved our ability to keep infrastructure expertise out of production environments and paved the way to deploy-only infrastructure (no upgrades).</li></ul><h3>Environment Review</h3><p>Part of addressing dev-ops includes ensuring that all developers maintained a clear understanding of the functions and maintenance that occur in the production infrastructure. One step to ensure this is to monitor it every day.</p><p>For 15 minutes the whole team steps through a set of metrics to review what happened the previous day. Occasionally something odd is found that initiates an incident response to investigate.</p><p>Over time this ensures that everyone knows, or at least hears about, the things that happen in production. This drives how they approach code/product design and therefore improves the overall quality of the products we build.</p><h3>Flexibility vs Rigidity</h3><p>An Agile mantra drives the idea of flexibility, or the ability to react to change. This is sometimes misunderstood as anti-process even though we all know that strict processes produce predictable results.</p><p>When teaching Agile we speak in generalizations about how a team should operate. When working Agile one must speak in specifics about the how a team should act. Both are critical perspectives for describing what Agile is and how to apply it.</p><p>A team’s actions require clear consistent process definitions that can be followed by everyone.</p><p>A team committed to a singular goal is most effective when following a disciplined process. Holding each other accountable for their actions and cooperating on delivering to the goal. Only with this working practice can a team excel.</p><p>This doesn’t mean that processes can not change. We practice following a rigid process that best serves our goals. We actively and intentionally adapt that process to improve how we deliver.</p><p>Over the last 7 years we have radically changed how we operate about every 3 to 6 months. Smaller changes happen more regularly when needed. Over that time some things have stayed consistent for longer, like Environment Review since its clear the practice works.</p><p>Ensuring each individual understands they are empowered to change how we work, and that those changes will be measured and improved on, and added to everyone&#39;s daily expectations, has become part of our strength.</p><h3>How we Change</h3><p>We all know change is hard and we all know it is necessary. A consistent complaint about how we change is that “it could have been planned better” or “we could have changed more slowly”.</p><p>We have tried different approaches with varying levels of complaining, though complaining isn’t a great metric to measure change. I think we have landed on the side of plan-a-little and change-fast, over plan-a-lot and change-slowly. It definitely feels painful when we are going through it, but the pain is short lived and the results pay off sooner.</p><p>This is not to say that all our changes have been good or well executed, just that a principle appears to be “get it over with”.</p><p>There are some innate mitigations to the pain of change that are part of the investment we make in our teams. For example, you will not see people sitting quietly waiting for things to work out, instead they are asking questions and complaining about the new obstacles in their lives. This active response to change ensures that any challenges created by the change can be overcome, the reasons for the change are propagated fast and everyone can be part of ensuring that those benefits are realized or the change failed and can be reverted.</p><p>The frequency of change and the fast approach also make everyone open and willing to experiment with new ideas. A change is received with questions instead of doubts, suggestions instead of resistance.</p><p>Processes are documented and followed. They are kept up to date because they change so frequently. Change creates chaos which much be managed with clear communication.</p><h3>What is Good</h3><p>We do a lot of things each day that make us good at delivering value. Most are obvious and have been talk about for years.</p><ul><li>TDD and Continuous Testing.</li><li>Regular releases.</li><li>Open work space.</li></ul><p>Some of the harder things we do with some level of success are:</p><ul><li>Empowering individuals to be responsible for shared success.</li><li>Identifying the simplest thing that works.</li><li>Owning the level of quality while delivery short term wins.</li><li>Trust in each other.</li><li>Personal portability of work location and team.</li><li>Open communication.</li></ul><h3>Simplicity</h3><p>Its worth saying a little more about keeping things simple because it is probably the most difficult part of software development.</p><p>The very nature of simplicity is subjective but if something is built and you don’t think it is perfect then you are feeling the right feeling and should just stop there.</p><p>Code is never finished so the ability to limit scope and deliver saves an enormous amount of time. Stating the balance with these statements:</p><ul><li>If you are selecting a framework you are probably over complicating the problem, until you need a framework.</li><li>If you need to select data from a database skip the ORM and use a lower level connection API, until you need the ORM.</li><li>Don’t work hard to write less code. Typing speed is not your long poll.</li></ul><p>We speak a great deal about perfect code and refactoring and keeping everything in a state that is easy to change. This it good but remember that code lives in a state based on the last change and is awaiting the next. Don’t be pedantic about “this” change and how perfect it must be.</p><h3>Prioritization</h3><p>Story prioritization is written about here “<a href="https://esumerfield.blogspot.com/2015/03/who-prioritizes-agile-stories-ops.html">Who Prioritizes Agile Stories. Ops, Security, Devs or the Business?</a>” and is a consistent conversation that requires regular attention, as it should, it is important.</p><p>Commonly confused aspects of this conversation include:</p><ul><li>The “business” doesn’t care that we release poor quality code. They do.</li><li>Developers always know how to balance quality and feature delivery. We do not.</li></ul><p>Delivery teams must own the definition of when a feature is delivered. Also, a delivery team is responsible for delivering features as fast as possible. This means they must for-go pretty code to benefit the customer first. This also means they must take the time to refactor their code so they can continue to deliver benefits to customers fast.</p><p>If this sounds fuzzy it is because it is. A good team must drive both conversations to hold themselves accountable.</p><h3>Conclusion</h3><p>The teams continue, the deliveries continue, the challenges continue. There is no magic to this, only open trust and a willingness to improve.</p><p>This technical, exacting, artistic industry we work in always has something interesting around the corner. Choose your future, not by the technology, but by the people you can create it with.</p><h3>References</h3><ul><li><a href="https://www.amazon.com/dp/B01GU387MS">The Art of Monitoring</a></li><li>Scaling Daily Stand-ups —<a href="https://esumerfield.blogspot.com/2015/01/tribe-level-ceremonies.html"> Tribe Level Ceremonies</a></li><li><a href="https://esumerfield.blogspot.com/2015/03/who-prioritizes-agile-stories-ops.html">Who Prioritizes Agile Stories. Ops, Security, Devs or the Business?</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf81aa656047" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>