Related Content
 |
3 Telltale Signs You’re Scaling Agile Too Quickly When an organization grows quickly, it puts stress on people, processes, and customers. Burnout happens, things fall through the cracks, and defects creep in. Unfortunately, many organizations try to scale agile too quickly, and that often leads to failure. Here are three of the telltale signs you're scaling too fast. |
|
 |
Is Your Agile Team Taking Every Opportunity for Communication? Scrum events are well-defined points where team members communicate, but they shouldn't be the only times. If you’re not considering coding, tests, and the delivery process as opportunities for a conversation, you are missing an important chance to leverage individuals and interactions, as the Agile Manifesto states. |
|
 |
A Definition of Done for DevSecOps In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps. |
|
 |
Slow Down to Speed Up Have you ever heard someone say, “How is it we never have time to do it right but we always have time to do it over?” When we rush to complete work, that's often when errors happen. It may seem counterintuitive, but slowing down may be one of the best ways to get the job done quickly—and right the first time. |
|
 |
Creating an Environment That Encourages Resilience Creating environments at work that acknowledge that failures will happen—and supporting the efforts team members make to recover—can help your organization become more effective. You cannot predict every challenge, but by embracing risk and providing opportunities for people to experiment, you can be more productive. |
|
 |
Dealing with a Change-Resistant Manager With almost any change, whether a trivial adjustment in procedures or a large-scale organizational change, people will vary in their receptiveness to it. But if you and your teammates have some good ideas to improve processes and your manager keeps shutting them down, you may be dealing with a change-resistant manager. |
|
 |
The Key to Avoiding Procrastination If you have a task you've been putting off, dividing it into small chunks is a good idea. But the real key to overcoming procrastination is just getting started. Once you begin, you’ve built momentum and are likely to keep going, doing a little more until you’ve made good progress—and maybe even completed the job. |
|
 |
Testing the Requirements: A Guide to Requirements Analysis Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day! |
