Related Content
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
|
 |
4 Ways to Restore Purpose to Your Daily Scrum The daily scrum was created to help the Scrum team meet its sprint goal. Unfortunately, answering the three daily questions can turn a synchronization and planning meeting into a status report. Here are four ways to make sure your team members are collaborating about their work and are ready to tackle the next day. |
|
 |
Designing an Office to Nurture Innovative Agile Development Teams Agile software development is a collaborative activity in many ways, but it also requires quiet time. While open office spaces foster communication and collaboration, it's still important for a workspace to have areas where people can buckle down and work. What is the best office configuration to nurture innovation? |
|
 |
Don’t Let Too Little Planning Tank Your Agile Adoption Many organizations turning to agile believe it means you don't have to do any planning. This couldn't be further from the truth. A healthy agile team does just as much (if not more) planning than a team using a waterfall methodology. Preparing and setting goals sets up the team for a more successful agile adoption. |
|
 |
If You’re Working Too Much, Is It a Challenging Project or Bad Management? Projects sometimes encounter challenges that require team members to put in extra work. But if this is happening repeatedly, it's worth figuring out where the pressure is coming from. You may need to ask, “Is this project simply challenging, or is it being badly managed?” |
|
 |
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. |
|
 |
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. |
