Venkatesh Krishnamurthy looks at some key ways to measure the business value of your project's agile performance. With consideration to the Agile Manifesto, Krishnamurthy uncovers different approaches to getting the most out of your user stories and defining true value.
Venkatesh Krishnamurthy asks: Can you build effective teams through games? Remember, team building is not a one-time thing—it is an ongoing exercise. It needs constant nourishment from the stakeholders and team members.
Scrum does not have any specific risk management practices as compared to the PMBOK. However, everything you do in Scrum—as well as any other agile method—will help you identify risk at an early stage. Venkatesh Krishnamurthy explains how to manage risks in agile projects.
Venkatesh Krishnamurthy explains how root cause analysis (RCA) can be used to help your team members avoid personal conflicts and resentment when a project fails. Conducting an RCA session can help to divert attention from people to process improvement.
Based on his own experience in delivering a large-scale agile project, Venkatesh Krishnamurthy shares with us a secret recipe for scaling agile projects. Apart from team size, tailoring practices to accommodate scaling plays a key role for successful implementation.
To succeed as an agile coach, you need to understand the skills and mastery that the position requires. Here, Venkatesh Krishnamurthy shares some tips that will help you coach an agile team. Remember, it has been found that successful leaders have creative traits rather than reactive ones.
Venkatesh Krishnamurthy writes that the stress and work expectations that led to Steve Ballmer's resignation from Microsoft are not uncommon in the IT world. The same pressure trickles down from the top to the delivery teams, spreading the negative effects throughout the company.