|
How to Train Agile Product Owners Using Financial Terms Prioritizing stories for an upcoming sprint can lead to confusion and miscommunication between the product owner and agile teams. But putting that exercise into financial terms, such as purchase, budget, cost, and investment—a set of words that everyone understands, no matter what their area of expertise is—gets everyone thinking about value.
|
|
|
Speak Up: The Key to Agile Success You can learn all the theoretical agile principles and best practices, but you still may not be agile. To be truly agile, you must also communicate and collaborate with your team—and this means speaking up. Even if you're not a natural extrovert, there are plenty of ways you can contribute during planning, sprints, and retrospectives to make your product and process better.
|
|
|
When Postmortems Meet Retrospectives: Improving Your Agile Process If you want secure, reliable systems, you need all stakeholders actively communicating. This means involving both IT operations and developers in discussions after deployments, to ascertain if anything went wrong and can be avoided, and what went well or could be refined. Integrating your postmortems and retrospectives facilitates collaboration and improves processes.
|
|
|
Transitioning to Enterprise Agility—and Bringing Outsourced Delivery Partners Along When companies adopt agile internally, they often forget to extend the concepts and values to their partners. You have to look at your outsourced delivery components as part of the process that needs to be included as an extended team. Collaboration, reflection, and improvement is at the heart of agile, and it should look that way from the perspective of all elements in the delivery chain.
|
|
|
Code Factories: Making Agile Work in Large Organizational Teams Making the transition to agile can be difficult for teams that are used to working in large groups and reporting to a single manager. Kris Hatcher suggests a new way to work: in smaller teams called code factories, which are created to stick with a specific product throughout its lifetime.
|
|
|
Is Your Product Owner an Overloaded Operator? Overloaded operators exist when an operator or operation has different meanings in different contexts. This usually applies to variables and sets, but it can be true for people, too. These people try to do the work of many different roles—and usually fail. If you have an overloaded people operator, analyze the work and try to divide it up.
|
|
|
Proactively Planning for Risks to Your Agile Project Being aware of risk is good project management common sense. But to address risk quickly and effectively when you encounter it, the best method is to establish clear, agreed-upon, communicated responses to risk before it even happens. Dave Browett suggests some tactics to mitigate and confront risk you can use with your team.
|
|
|
Kanban for Software Testing Teams Kanban, a highly effective agile framework, is based on the philosophy that everything can be improved. And it's not just for development teams. The QA team also can use kanban to organize tasks, identify bottlenecks, and make their processes clearer and more consistent.
|
|
|
Move Past Your Comfort Zone: Use Imposter Syndrome to Your Advantage When you're speaking, teaching, or coaching, do you ever suddenly feel like you're in way over your head? That there must've been a big mistake, because you're not qualified? Instead of letting this imposter's syndrome paralyze you, there are ways to embrace being outside your comfort zone and turn your self-doubt into a chance to thrive.
|
|
|
The Real Key to Agile Success: Communication Think about the common practices of an agile team: daily stand-up meetings, retrospectives after every sprint, pair programming and buddy reviews, collaborating with customers, and more face-to-face time instead of mountains of documentation. What is the agenda behind all these operations? Frequent and open communication.
|
|