scrum
What's in the September/October 2014 Better Software Magazine? In our latest issue of Better Software magazine, the feature articles focus on software licensing and ways to improve your team’s approach to process improvement. Creating software for a wide range of platforms is difficult enough, but enforcing software licensing also can be challenging. |
||
Tips for Improving Your Geographically Distributed Agile Team Many people on agile teams have at least one person who is not collocated. Those on collocated teams indicate that more of their projects are successful; those on far-located teams have the highest number of challenged projects. What can you do if you're part of a geographically distributed team? |
||
Managing Risk in an Agile Project 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. |
||
Book Review: The Retrospective Handbook Steve Berczuk reviews Patrick Kua's book The Retrospective Handbook: A Guide for Agile Teams. Among the issues Kua addresses are how to lead a retrospective when you are part of the team and how to deal with retrospectives with distributed teams. |
||
Four Reasons to Stick with Daily Scrum Meetings Every team member is required to attend a daily scrum meeting. Pro tip: The ScrumMaster and product owner are team members too, despite their titles of leadership. If you feel you don’t need to attend every daily scrum, then consider these four reasons why you should stick with it. |
||
Seven Steps for Starting Scrum Project taking a long time to get out of the analysis phase? Is there ambiguity and a lack of transparency in all moving parts? Is your project on its way to becoming a money pit? If you answered yes to any of these questions, it might be time to start using Scrum to save your project. Read on. |
||
The Secret Recipe for Scaling Agile Projects 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. |
||
Is Scaling Agile an Oxymoron? The success of agile methods has meant that larger projects also want a share of the benefits. But as compelling as the idea might be, is scaling agile an oxymoron? Isn't it contradictory to expect large and complex projects to be agile? Or would such an attempt inevitably lead back to waterfall? |