Related Content
 |
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. |
|
 |
Wonder Woman and Google Get Girls Coding This Summer To help ensure that today’s Wonder Girls (and guys) have coding superpowers that will help them in the future, Google announced the company has joined forces with Warner Bros. Pictures to release a new interactive coding project via Made with Code. |
|
 |
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. |
|
 |
Breaking Down Your Development and Testing Walls Testing earlier assures better quality. But maybe most important, things like agile and DevOps—which encourage that you shift your testing left and allow for more collaboration between different parts of your team—have broken down the walls that previously separated testers for the rest of the organization. |
|
 |
Finding the Bottlenecks in the Agile and DevOps Delivery Cycle To achieve incremental software development and continuous feedback, you need to eliminate the tasks that create bottlenecks, which hinder the flow of development. A chain is no stronger than its weakest link, and identifying these “weak links” is a critical step toward achieving agility and increasing efficiency. |
|
 |
Before You Can Eliminate Agile and DevOps Bottlenecks, You Need to Identify Them Agile and DevOps, which now dominate software development, lean on continuous integration, continuous testing, and continuous deployment. Because of that, anything that might break this iterative and continuous cycle could throw everything out of whack and stunt your team’s growth. |
|
 |
Think Small: Break Down User Stories for Agile Success The entire agile team needs to be involved in a continuous process of identifying ways to simplify work, right up until a story is complete. Smaller stories ensure that development work is rapid and trackable. Mitch Goldstein details how to focus on breaking stories down into a more estimable, “digestible” size. |
|
 |
Test Your Data Quality to Increase the Return on Your QA Investment With the high volume of data coming into your organization, it’s important that it be complete, correct, and timely. But considering the velocity at which this data is moving, how do you measure its current quality? You must be able to test it wherever it sits still enough to be viewable, without altering it. |
