Related Content
 |
When Transitioning to Agile, Let Value Be Your Guide When making a transition to agile, it’s important to get a common understanding of what you’re trying to do, of how things are currently done, and of the definition of done. In a value stream analysis, you can identify where major chunks of time are being spent (and why), and then start prioritizing based on value. |
|
 |
Beware Confidence Masquerading as Competence Self-confidence is essential to tackling difficult problems. Where we need to be careful is not being falsely overconfident. What’s behind that overconfidence can either help or hinder your solving issues and achieving a good result. Here's how to make sure that confidence is backed up by competence in your team. |
|
 |
6 Ways to Share Negative Feedback in a Retrospective Negative feedback has the greatest potential to help people change in areas that can have a lasting impact. But sharing negative experiences and criticism can often be a challenge and may cause more harm than good. Here are six tips for sharing negative experiences effectively and building trust along the way. |
|
 |
Are Headphones Hindering Your Office Communication? With all the chatter going on in offices, people often turn to headphones to block out the noise and be able to concentrate. Noise-canceling headphones block out distractions, but they can also block out communication. It may be a good idea to set some boundaries for their use so employees can still collaborate. |
|
 |
Brain Hacks to Engineer an Agile Transformation When we are presented with a decision, the subconscious determines what we’re most emotionally comfortable with, then fills in the gaps to justify choosing it. In other words: Our brains lie to us. Then how can we ever get out of our comfort zone? Believe in change and take an agile approach to incremental adoption. |
|
 |
Is Everything Code? As modern software processes become automated, one might argue that nearly everything in software development is code. Obviously, our software applications are comprised of code, but that’s only the start of it. Our tests, delivery orchestration, and someday even our software production could be automated. |
|
 |
The Agile Culture You Need for Faster Pull Requests Is your process for pull requests compromising your team's agility? You can structure your changes in a way that facilitates more rapid feedback, but even then it is still possible to have a slow integration time if people don’t review pull requests promptly. Mechanics are part of it, but culture also matters. |
|
 |
How to Talk to Executives about Agile In the agile community, executives tend to get a bad name. They are accused of not understanding agile and the benefits it will bring their companies. But we just need to speak the same language: Look beyond the surface-level reasons for resistance and try to identify the financial grounds. Just follow the money! |
