Agile project management has entered the mainstream – incremental delivery is now common and (should be) expected for any new software development project. Which agile development methodology should you use on your project? There are at more than ten to choose from. What makes them different? The risks that they try to address.
Business Analysis / Product Management / Requirements / Requirements Models / Use Cases
Posted on:
How To Write Use Case Preconditions and Triggers
Use case writing is key to effective requirements management. Each use case represents a single idea or logically grouped behaviors. When you define a use case, there are several mistakes you can make. Preventing those mistakes is the first order of business. The second order of business is making sure that the use cases in the system work together. This requires an understanding of the context in which the use case happens. To fully understand a use case you have to know what is promised to be true before the use case happens, as well as what causes the use case to happen. These are subtly different.
Business Analysis / Communication / Consulting / Presentation / Requirements / Writing
Posted on:
Effective Communication of Requirements
Effective communication of requirements requires more than documentation and broadcasting. Effective communication requires interaction and collaboration. Alistair Cockburn addresses this in his analysis of project successes and modes of communication.
Product Management
Posted on:
Ten Ways To Be A Better Product Manager
In product management training, we spend a lot of time focusing on what we do. Adrienne reminds us that this isn’t enough, we also have to focus on how we do it, with her tips on how to be a better product manager.
Product Management / Software development / UX
Posted on:
Product Management and User Experience
There’s a buzz going around about the conflict and collaboration between product managers and user experience professionals. It started with a pair of articles co-written by Jeff Lash and Chris Baum. In short, with a user-centric view of products, both roles are responsible for the success of the user-interactions. Who makes the decisions?
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-03-03]
A look back at the best from a year ago.
Project Management
Posted on:
Project Scheduling – 80% Done, 80% Remaining
Johanna warns us that there is “no such thing as percent complete” when it comes to tracking status on a project. Your managers and customers want to know percent complete – and there is a way to report it. Project planning and scheduling involves walking this fine line.
Product Management / Project Management
Posted on:
Scheduling Product Releases
When you define a product roadmap, you also define the release dates for your product. Change happens. Your market changes, your customers change, your requirements change. Unpredictable events happen. Your competitors release a new killer feature, your developers have an epiphany (or run into a roadblock). Should you change your release schedule?
Agile / Product Management / ROI / Software development
Posted on:
Agile Development and Software Maintenance Costs
Over 90% of the cost of software development is software maintenance (cite). This alarming trend was predicted as early as 1972. McKinsey suggests that CIOs should spend no more than 40-60% on maintenance. Gartner’s IT Spending and Demand Survey (2002) reports that CIOs are spending 80% of their budgets on maintenance (p12 of presentation). Agile development can help reverse this trend.