Documenting user requirements is always a challenging phase in software development, as there are no standard processes or notations. However, communication and facilitation skills can make this activity easier. Here are five techniques for converting user stories into testable requirements.
Single-point estimates, whether they are for a budget or a schedule, are never correct. Things happen. Demanding that your team provide you an exact number and then treating that as a guarantee is not being a good manager—or being agile. What if you could provide a different estimation leadership?
This issue of Better Software gives best practices that will improve your skills in a variety of categories, including agile, testing, DevOps, and process. These articles aim to better your professional lives so that you and your team can deliver software technology that delights customers.
Testers are very much still needed. However, with so many new technologies and roles becoming available, some testers may want to explore options for their career paths. Michael Sowers offers an agile approach to determining your career direction, evaluating the alternatives, and developing a plan.
For agile to work, it's important to evaluate how your team and your project are doing. Qualitative feedback, such as from reviews and retrospectives, can be valuable. But at some point you may need more quantitative information to improve your project. How do you decide what metrics to gather?
The upcoming Agile Development, Better Software & DevOps Conference West in Las Vegas features four incredible keynote speakers with very dissimilar but equally important topics. Lee Copeland, program chair for the conference, summarizes the keynote presentations and tells you what you can expect.
Like agile, people are quickly adopting and making great use of DevOps, which stresses communication, automation, and a strong sense of cooperation within a team. Yet, while it can be argued that agile spawned DevOps, some software veterans argue that it’s DevOps that’s actually pushing agile.
Agile teams run like a well-oiled machine, so it’s important to take a look at your group and assess just how agile it really is. What fixable problems might you be experiencing that are jamming up the system, causing the process to run slower than it needs to?
In your quest to figure out how your team is doing with its agile process, gathering data can be useful—as long as it does not add significant overhead to your project or get in the way of delivering customer value. Don't let the desire to quantify your improvement get in the way of improving.
The role of demonstration in a sprint review often takes on more importance than it should, even to the extent that some teams refer to the review as a demo. By focusing on the demo you risk having the team do all the talking, rather than a two-way conversation between the team and the stakeholders.