Related Content
 |
Making Continuous Integration Work for You Many developers learn about using continuous integration to improve their deliverability speed and decrease the amount of effort needed to launch new features. Actually practicing continuous integration, however, is nowhere near as straightforward as it sounds. Here's how to get started in making CI work for you. |
|
 |
You Can’t Rush Agile Change Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid. |
|
 |
16 Questions to Assess Your Response to Major Change If your responsibilities include guiding others through major change, you might find it instructive to assess your own behaviors and response to change. The sixteen questions here can help you do just that. You can also use these questions to facilitate a discussion with your team about a current or upcoming change. |
|
 |
Measuring the Effectiveness of Your Vulnerability Discovery Strategies Trying to prove an app has no vulnerabilities is fraught with challenges, so teams need to choose appropriate strategies for securing apps and ways of measuring whether the time and money spent searching for vulnerabilities is effective. This means understanding how metrics apply to your specific environment. |
|
 |
Defining Velocity for Your Agile Team When an agile team talks about velocity, it's usually how much functionality they'll deliver in a sprint, often based on historical data about the number of story points the team tends to finish. But you shouldn't use velocity as a measure of success for your agile process. Make sure everyone knows what's important. |
|
 |
A Checklist for Managing Go-Live Decisions and Risks If you have to replace a complex existing data system in production, decisions about when and whether to go live should be treated with gravity and care. One process that can help keep you honest is developing checklists that describe very clearly what is expected to be accomplished and verified at each milestone. |
|
 |
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. |
|
 |
Why the Burden of Security Should Be Assumed by the Entire Team Quality can be improved over time, and while it’s difficult to change perception, it’s still possible. But poor security can sink your ship before it even leaves the dock. Invest in the security of your application and be sure to spread that responsibility to multiple levels of your software team. |
