Studies and experience show that higher quality and better value solutions are achieved by projects that attain a thorough and unambiguous understanding of business and user requirements. Adrian Reed looks at how requirements can help avoid project failure and waste.
Assumptions are a fact of life. Without making assumptions, it’s unlikely that many decisions would get made, and certainly fewer projects would ever get launched. However, sometimes assumptions come back to haunt us. Adrian Reed looks at how to handle assumptions when working on projects.
There are two ways to think about scope—a list of things to be done or a list of goals to accomplish. As long as scope is defined as a list of things, then your project process is not agile, even if your team is using the mechanisms of agile development within the code creation cycle.
The Chicago Board Options Exchange (CBOE) trading system recently was shut down for part of a day due to a software glitch. Some inside the CBOE are looking to recent configuration changes, requirements tracking, and testing as possible culprits.
Product managers know that a product needs to be simple to succeed in a market. Although being simple is a product virtue, being simplistic can be a product vice. Scott Sehlhorst evaluates why it's better to create a product that is simple—not simplistic.
Strategy is important not just because you want to be intentional but also because strategy makes you more efficient. Strategic activities ensure the intended product is the right product. Scott Sehlhorst looks at why a strategy is not a plan; instead, strategy guides planning.
The current information technology trend is that of survival of the fittest, where players thrive based on success factors such as releases of new products that are feature rich, user experience driven, and performance focused. Rajini Padmanaban looks at where the new product ideas come from.
Software architects typically don’t own the products that individual teams are creating, yet they help define a cohesive approach to developing the products and are often responsible for defining how different products interoperate. Scott Sehlhorst looks at the idea of architecture stewardship.
Brainstorming is an extremely useful tool in business analysis. In order to yield maximum results, brainstorming sessions need to be well planned and consider the needs and preferences of the attendees. Adrian Reed provides useful tips for preparing a brainstorming session.
Author and software consultant Gojko Adzic recently gathered together a group of professionals to discuss software delivery and business outcomes, and to identify the core ideas that could be shared with delivery teams to help them focus on building the right things.