Related Content
Overcoming Test-Driven Damage Some say test-driven development may work well initially, but as soon as we start to refactor our code, it breaks old tests and requires us to write new ones. This is not the fault of TDD; it’s the way we’re using it. TDD remains a valuable way to verify code as we write it, so we need to repair our test-driven damage. |
||
The Present and Future of AI: A Slack Takeover with Raj Subramanian Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Raj Subramanian, who works with self-healing, AI-based test automation, hosted this Slack takeover to discuss all aspects of AI: testing it, its biases, where it is now, and where it's going. |
||
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. |
||
Developing a Clear Project Communication Plan When planning a software project, you need a thorough project communication plan. Both managers and developers need to take part in formulating the plan so that the correct terms of reference are present, achievable goals are set, and deadlines are attainable. Clear communication is essential. Here's what to include. |
||
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. |
||
4 Tools to Make a Project Manager’s Job Easier A project manager is responsible for working out all the details of a project. They have to come up with a strategy to work with the team to overcome hurdles in the way of the project’s goals, and they have to accomplish it all without overstepping the budget. Here are four tools that can help keep it all straight. |
||
Take Credit for Your Risk Management Activities If you have an important implementation date, early identification of the minimum viable product is a vital risk-management step that helps focus your team’s attention on what's important. Rather than apologizing for intelligent phasing of functionality to manage risk, explain it to stakeholders and take credit. |
||
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. |