Developers Developing Development
:part 2
If you are one of my millions of dedicated fans 😎, you will be familiar with part one of my exploration into software development practices, which politely scratches the surface of the waterfall model and rapid application development (RAD). In part two of this journey, I will take a general look at Agile Software Development and a framework known as Scrum.
Agile Software Development comes from years of experience practicing rapid application development. In February 2001, a group of seventeen software engineers met and put together the Agile Manifesto, which is conveniently available to download here. The Manifesto centers around four main values:
Individuals and interactions over processes and tools
- Having competent people working together effectively is more important than the process and tools used
Working software over comprehensive documentation
- Having a product that works is more important than having super detailed documentation. Documentation is of course important, but other techniques, like the waterfall model, focus on it in a way that almost becomes restrictive.
Customer collaboration over contract negotiation
- Having the costumer involved during the production steps makes more sense than having strict contractual deadlines.
Responding to change over following a plan
- As we learned when comparing the waterfall model with RAD, the ability to adapt while building the product leads to completing a project in time and on budget.
These statements can seem harsh at first, but it is important to note that the process values all of the items in the above list, but the items on the left in bold are valued a bit more and are thought to be more effective if focused on.
The Manifesto also highlights 12 principles:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity — the art of maximizing the amount of work not done — is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
I know what you’re thinking: “those copy-paste skills are on point!” 😎 These 12 principles seem to simply be a deeper look at the core values. They highlight the need to have face to face interactions and open communication with the customer, while emphasizing team work that should be able to govern itself. On a side note, the self governing teams and self reflection are very reminiscent of the idea of smaller companies working as tribes, detailed in the book ‘Tribal Leadership’ by Dave Logan, John King, and Halee Fischer-Wright.
Get Dan Fyfe’s stories in your inbox
Join Medium for free to get updates from this writer.
Agile Development is a broad term that covers a general way of thinking when it comes to developing software. There are many branches and processes that come from agile development. I plan on looking into more specific examples in the future, but first a quick look at something I came across while looking into all of this: Scrum, which you can find the complete guide to here.
Scrum is not a process or technique in itself. It is a framework that has been used since the early 90’s to employ processes, manage workflow and helps with the overall understanding of the effectiveness of that process. Scrum works through empiricism, which is a fun way to say that it runs on the idea that knowledge comes from experience and to make decisions based on known data. It has a somewhat rigid structure of values, teams and events. Scrum works in an iterative way to assure the data and predict risk in a project. Scrum sits on three basic pillars:
- Transparency — a process must be defined and referred to in a way where everyone knows what is going on. Language must be clear and everyone needs to have the same definition of ‘done’.
- Inspection — frequent inspections of progress are needed to make sure everything is on track, but should not be frequent enough to cause a disturbance.
- Adaptation — if, at any point during the process, progress is deemed unacceptable, the process must be adjusted as quickly as possible to make sure everything is on track.
Scrum Teams are self-organizing, meaning they decided how to get their work done, and cross-functional, meaning they have all of the elements and skills needed to accomplish their goal. They fall into these categories:
- Product Owner — one person who is responsible for managing the Product Backlog, which is an ordered list of everything that is needed in the product and is the single source of requirements for any changes that need to be made. The Product Backlog evolves as the product evolves.
- Development Team — self-organizing, cross-functional, small enough to be nimble, but large enough to get significant work done. Scrum does not allow for titles in a Development Team, regardless of what they do. Each team member might have a specialty or an arguably more important job, but everyone is accountable to get everything done.
- Scrum Master — exactly how it sounds. The Scrum master advices and shows all other members of the teams the rules and flow of Scrum to help everyone understand the steps and why they are important.
Scrum Events are used to create structure and regularity to the process and have a set, maximum duration. The main event in Scrum is called a Sprint. A Sprint is usually timed to be at maximum, a month or less long and a new Sprint starts immediately after the last Sprint ends. A Sprint is made up of:
- Planning — when the Sprint is planned. Time allocated for planning is a maximum of 8 hours. The entire Scrum team works on these details. The team decides what will be done during the Sprint (Sprint goal), why it’s being done, and how they will do it in the Increment.
- Daily Scrum — A 15 minute daily meeting to discuss what happened the day before, what will happen today, what troubles are keeping the team from making progress.
- Development Work — After the Daily Scrum, the Development team creates their own plan and starts their work.
- Review — After a Sprint ends, a review meeting, maximum 4 hours. The attendees of the meeting include the Scrum team as well as product stakeholders. They discuss what elements of the Product Backlog were completed, any problems that arose, how they worked passed those problems, and how the next Sprint could be better. An important part of these meetings is a review of the product and how its marketplace and use might have changed, which would, of course, change the approach to development. At the end of the review, the Product Backlog is revised for the next Sprint.
- Retrospective — This is the Scrum team’s chance to use the review to plan improvements for the next Sprint. The meeting, maximum three hours, allows the team to focus on everything that went well, or went poorly, and objectively use that information to make formal improvements for the next Sprint.
Conclusion:
- Agile Development seems to be the best general guideline to getting things done. It focuses on letting people get work done in a collaborative, peaceful manner. Its principles define the importance of working with the customer in an iterative and adaptive way. I look forward to taking a deeper dive into the different implementations of agile development (one is called Extreme Programming, which is super exciting 😎).
- Scrum is also pretty interesting. The daily work in my last profession was not long term enough to have any real structure most of the time, so it was interesting to find that things like Scrum exist. It makes a lot of sense, of course, but it amazes me to see how much work goes into making sure work gets done in a clear, organized way.
Sources:







