Process

Articles

Cloud with tools graphic Fixing a Broken Deployment Process

When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.

Colleen Stock's picture Colleen Stock
Continuous improvement How Businesses Stay Agile: The Art of Being Retrospective

The greatest use for agile in business is in changing how you tackle problems and projects. Rather than defining the whole project and setting a “way forward,” an agile approach takes things much more iteratively. That means meeting as a team on a frequent and regular basis to share problems and successes, then making improvements as needed—being retrospective.

Ivan Seselj's picture Ivan Seselj
Man surrounded by sticky notes Streamline Your Agile Requirements by Avoiding Bloated Backlogs

In agile development, a bloated backlog results from teams accumulating huge lists of requirements, usually in the form of user stories. Retaining every possible story for building the product weighs down the backlog while squeezing (or obscuring) the highest-value stories. The best way to help minimize this risk is to optimize the time spent defining and refining the product priorities.

Michelina DiNunno's picture Michelina DiNunno
Model airplane Build One before Building Many: Learning from Agile Feedback

When you're working on a project and are presented with a big story or requirement, resist the urge to treat it as a single piece of work. One of the principles of the Agile Manifesto is to deliver working software frequently. This allows you to learn from what you built and make adjustments. See if you can break down the request and find a small piece of work within the big.

Allan Kelly's picture Allan Kelly
Leader on a team 7 Lessons Agile Can Teach Us about Leadership

The Agile Manifesto contains values to guide teams toward developing better software. But its directives are also about leadership—influencing culture and creating an organization where people can collaborate to meet the needs of their customers. Here are seven lessons the Agile Manifesto can teach us about leadership.

Ryan Ripley's picture Ryan Ripley
Woman designing software architecture An Agile Approach to Software Architecture

For an organization transitioning to agile development, creating software architecture isn’t incompatible with your new processes. Consider the principles in the Agile Manifesto, involve team members who will be using the architecture in its development, and reflect and adapt often, and you will end up with an architecture that meets the needs of your team and your enterprise.

Gene Gotimer's picture Gene Gotimer
Six steps 6 Steps to a Successful DevOps Adoption

Implementing DevOps practices can significantly accelerate software releases while still assuring applications meet quality objectives. But DevOps can’t be bought, bolted on, or just declared. If you’re considering a move to a DevOps delivery model, here are six approaches for ensuring a successful DevOps adoption within an organization.

Alan Crouch's picture Alan Crouch
Hand holding stopwatch 5 Principles for Using Agile Team Metrics Responsibly

With the transparency of agile and the granularity of team-based metrics, it's important to be responsible in how you use your measurements. There are five principles Joel Bancroft-Connors adheres to when dealing with metrics: start collecting early and often, be consistent, stay focused, measure the project and the teams separately, and—most importantly—measure responsibly.

Joel Bancroft-Connors's picture Joel Bancroft-Connors
Transparency The Transparency Experiment: Improving Accuracy and Predictability in Scrum

Using the iterative and incremental agile development framework Scrum should help manage product development, but some teams still have difficulty delivering features in a predictable manner. This organization decided to address the mismatch between what was being committed and what was accomplished by doing an experiment in work transparency.

Uncertainty Reduce Uncertainty in Agile Projects with #NoEstimates Thinking

Estimation uncertainty in software projects is often not driven by the difficulty of the problem we are trying to solve, but rather by the health of our codebase, the quality of process, and how much discipline we have in our management practices. If you want to improve your estimates, then agile and #NoEstimates thinking can have the biggest impact on your team’s success.

Ryan Ripley's picture Ryan Ripley

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.