When we think of planning, we often think about requirements planning. We get the initial features and functions down, and then see where agile takes us. Lisa Calkins claims that less than a third of software development projects are successful. Regarding this lack of success, process...
At a time when organizations of all sizes both want and need innovation, exciting approaches including lean startup and agile development have risen to the forefront. Although there is no shortage of resources and expertise on these approaches, less guidance is available on the daunting...
Undoubtedly, your organization has disaster plans in place for recoverable situations. But what about for going out of business? Thinking about your obligations to clients, users, customers, and partners before the worst happens can make the transition easier for everyone. Here are some people and things you should incorporate into your apocalypse plan.
A different perspective can give you a whole new approach to work. Here, László Szegedi suggests that the next time you need to plan something, you think backward—visualize your goal, then reverse-plan to map the whole process that leads to that result. He gives examples for simple tasks and for higher-level test planning.
In this FAQ column, Arlen Bankston highlights the difficulty many companies have making the full transition to agile, straddling between waterwall ways and the new horizons of agility. Arlen provides techniques that can enable companies to ease into the transition, allowing their organization to make the adjustments without the burden of large plans and commitments.
Performing all the functions required to facilitate project teams as ScrumMaster can be a task. Zuzi Sochova describes creative ways to become a master of Scrum by adopting a ScrumMaster state of mind.
Testers who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid.
As real and daunting as scheduling pressures can be, they have to be balanced with the consequences of a potentially disastrous premature go-live. Don’t let all the reasons a system simply "must" be implemented by a target date overwhelm compelling evidence that it is not ready. Consider these eight questions honestly first.