Related Content
 |
Revitalize Your Problem-Solving by Conducting a Solution Analysis When you're solving a problem, it's a good idea to analyze a solution you come up with before implementing it. One way to do that is to ask what’s good about a proposed solution and what’s bad about it, focusing in particular on the impact of the solution. This way you can be sure you've thought everything through. |
|
 |
5 Tips for Making the Most of Your Agile Meetings People think agile entails too many meetings, but usually that complaint has nothing to do with the number of meetings, but rather the way they're run. New agile teams often do everything together because they think that’s what agile expects, but that's not true. Here are five tips to better run your agile meetings. |
|
 |
How to Communicate to Build Trust on a Scrum Team Trust among the ScrumMaster, product owner, and development team is essential to making the process work. Transparency, inspection, and adaptation are the three pillars of Scrum, and you can't commit to these actions if everyone doesn’t have openness and respect for each other. Communication is the best way to do that. |
|
 |
Software Testing and Development Is Now a Team Sport One person might be the spark that starts the fire, but it takes multiple people to help keep the flame burning. Developers and testers rely on each other more and more these days, and you need to be able to pass something along to someone with different talents in order to successfully reach the finish line. |
|
 |
Choose Continuous Integration over Branching for Faster Feedback Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information. |
|
 |
Engineering Architecture Systems for a Faster Build In the era of continuous integration and continuous deployment, big applications are creating bloated build pipelines. The problem is when code becomes so entangled that every change impacts large portions of the system, meaning there’s a lot to rebuild. If you reshape the code architecture, you can reduce build times. |
|
 |
Make Your Security Testing More Agile Security practices traditionally have followed a waterfall model, adding security testing on at the end. Organizations need to coach their security programs and testers to prioritize analysis and risk, much like we do with agile stories, to better incorporate security defects with other feature work along the way. |
|
 |
What’s Your “Size” of Agile? There are approaches to agile that sound great on paper, but will they really be the best choice for your team in practice? Instead of standardizing on any form of agile, think about the results you want. Why not create the environment that works best for you? There's more than one way to do agile. |
