Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.
Lawrence Putnam explains whether or not big agile is an enterprise savior or an oxymoron. What if agile only works when teams and projects stay relatively small? That’s the question most CIOs want answered before investing scarce time, energy, or resources chasing the big agile paradigm.
Enterprise development organizations are increasingly embracing agile as a concept, if not entirely in practice. That’s because adopting and scaling agile methodologies for large, complex enterprise software projects can seem daunting. Larry Ayres shares some tips for scaling agile development for enterprise software.
In today’s fast-paced workplace, software developers and project managers are confronted with a painful paradox. They are faced with continual pressure to accelerate the development process, but this “need for speed” can result in communication failures—and the accompanying project and quality problems.
Adam Yuret explains what can go wrong when teams blindly commit themselves to sprints; collaboration and quality suffer when we pressure people to work themselves to death by forcing them to promise things they cannot yet understand. Investing in systems-thinking approaches to improve the lives of our workers will pay dividends in improved quality, engagement, and creativity.
A health care crisis can hit without warning, leaving you both nursing the patient and mired in seemingly endless bureaucracy. In this article, Kathy Iberle shares with us her experience dealing with an elderly uncle who suffered a stroke and how agile methods, like using a visual planning board, can help one prepare and be ready when disaster strikes.
Holly Bielawa explains that being a a requirements craftsman means that you need to test your assumptions in real time while developing a product. Then you pivot as needed, change your business model as you learn, and constantly get out of the building and gather data to determine your minimally marketable product.
Charuta Phansalkar writes on the necessity of capturing and understanding requirements using agile practices. Agile, when implemented effectively, will ensure that the customer's voice is clearly understood throughout the project, which results in maximum customer satisfaction.
The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework.
Terry Wiegmann writes about how Microsoft Word's features, like its spelling and grammar checkers, can help one identify agile smells—those signs that something might be wrong. While we may want to minimize documentation and the use of Word, we can mentally use some of Word’s features to sniff out some whiffs of smells.