Related Content
 |
How to Say "No" When Asked for Help Collaboration among team members is what makes agile software development both effective and fun. Being part of a team means not only helping others so that the team makes progress but also asking for help when you need it so that you don’t block the team for too long. |
|
 |
The Right Way to Split User Stories One of the key techniques in the mechanics of agile software development is the splitting of epics into stories. Scott Sehlhorst highlights examples of ways to split user stories and discusses the debate between breadth-first and depth-first development. |
|
 |
Dodging the Requirements Hazard Tacit knowledge includes the knowledge that business stakeholders possess that isn’t codified or written down anywhere—and information they don’t even know they possess. The challenge for business analysts is that it is essential to get at this type of information in order to write requirements. |
|
 |
Hiring Technology Product Managers: The Latest Scott Sehlhorst looks at an analysis of how companies are posting requirements for hiring new technology product managers in the US—including the trend of placing more importance on domain experience than product management experience. |
|
 |
Business Analysts—Don't Hide from the Data Model Among business analysts, there is often a real reluctance to model data as it is seen as a technical activity rather than a business-focused activity. Adrian Reed explains why data models are important, and how they can help map out and understand the problem domain to avoid misunderstandings. |
|
 |
Don't Let "Good" Ideas Go Bad! Organizations need new and innovative ideas to solve complex problems. However, sometimes "good" ideas can be the very reason behind problems. Systems thinking and following the Golden Circle can help. |
|
 |
How to Write Good Software Requirements Even in 2013 software professionals are still having difficulties getting good software requirements. Joe Townsend lists several handy resources on how to finally start writing quality software requirements. |
|
 |
Become a Better Product Manager: Your Project Deserves It Becoming a better product manager is something you never stop doing. As you get better, your work will improve, your satisfaction with your work will increase, and opportunities to do even better work will come. Scott Sehlhorst sums up how to invest in becoming a better product manager. |
