Related Content
You Can’t Rush Agile Change Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid. |
||
How Failed Agile Transformations Can Still Have Value Not all agile transformations are successful in the same way; in fact, it’s possible to get tremendous value out of a failed attempt. A team that doesn't end up fully transitioning to an agile framework can still borrow some lessons from agile development methods to improve their processes. |
||
Agile for Everything: Taking the Manifesto beyond Software The values of the Agile Manifesto, while written to apply to software, can form a basis for an adaptive approach to any project. Going from specific to general and inspecting and adapting along the way are great design ideas, no matter what you’re working on. Here's how to use feedback to take agile beyond software. |
||
Helping Introverts and Extroverts Work Together The personality tendencies of extroversion and introversion concern where people get their energy, and this is key to understanding how coworkers can perceive—and sometimes misinterpret—each other’s behavior. If the introvert-extrovert dynamic poses challenges, consider discussing these differences as a team. |
||
What Aircrews Can Teach DevOps Teams Aircrews learn a set of skills involving a structured way of communicating that breaks down barriers and forces an honest evaluation of the issues. They also automate what they can but still practice their craft over and over again, including what to do during failures. DevOps teams can learn a lot from aircrews. |
||
How to Deal with Coworkers' Irritating Behaviors like an Adult Annoying behaviors are amplified in an office due to close quarters and personal preferences. No one likes to have an awkward conversation—especially when it’s with someone you have to face every day—but if a coworker's behavior is driving you up the wall, be a grown-up and let them know. Here's what to say. |
||
Why the Minimum Viable Product Matters The MVP brings tremendous value to a team’s ability to effectively implement agile practices. It also allows us to better understand what “value” actually means to our users and how context changes the meaning. Your MVP must move through your validation and release cycles while still being valuable to your users. |
||
5 Tips for Mentoring Future Mentors Being a mentor is a big responsibility. It becomes a greater one when the person you're mentoring is set to become a mentor to someone else. What advice would you impart to your mentee? What do you wish you'd thought of when you were starting out as a mentor? Payson Hall distilled his experience into five principles. |