Related Content
Stewardship in Agile Software Architecture and Design 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: A Great Tool for Business Analysts and Everyone 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. |
||
How to Identify Disengaged Employees—and Increase Productivity Productivity can be difficult to increase but is usually easy to decrease. Undermotivated or unhappy employees spread discontent and use idle time to sidetrack their teammates. Identifying disengaged employees and removing them as a distraction will make everyone on the team more productive. |
||
Are Most Meetings a Waste of Time? Despite the many articles on holding fewer meetings, there doesn’t seem to be a difference in the number of meetings being held. As many as 85 percent of managers think their companies’ meetings are unproductive. How can you prevent your meetings from being a waste of everyone's time? Read on. |
||
A New Software Development Manifesto for Building the Right Things 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. |
||
The Outside-In Approach to Product Positioning Early on product positioning helps drive focus and clarity for the team and allows a stakeholder to approach funding decisions from a strategic perspective. Scott Sehlhorst highlights some outside-in approaches to product positioning and their benefits. |
||
How and When to Use Best Practices Organizations often waste time and effort by applying best practices without tailoring them to their own unique circumstances. Does that mean you should ignore best practices? Of course not. Here are some questions to ask to be sure you're using best practices in the best possible way. |
||
Why Do We Continue to Fail at Requirements Management? Joe Townsend examines why software professionals continue to fail at requirements management (RM). Some of the ways to address RM issues include using the right RM tools, proper requirements prioritization, and requirements churn. |