Page: 1 2 3 4 5 6 7 8 9 <prev | next>
Project managers and business analysts share many challenges and concerns, particularly in the areas of requirements, communication, stakeholders and professional development. Here are seven emerging trends, ranging from smaller projects to fewer emails, that BAs and PMs should be tracking and leveraging in 2014.
Organizations are releasing software as soon as possible, skimping on Quality Assurance, squeezing testers, and pointing fingers when it all goes wrong. As our series concludes, we look at the final two reasons that they should just do away with software QA completely (but not really).
Organizations are releasing software as soon as possible, skimping on Quality Assurance, squeezing testers, and pointing fingers when it all goes wrong. As our series continues, we look at the third of five reasons that they should just do away with software QA completely — that is, management needs scapegoats.
Organizations are releasing software as soon as possible, skimping on Quality Assurance, squeezing testers, and pointing fingers when it all goes wrong. As our series continues, we look at the second reason they should just do away with software QA completely — to test the code of the smartest programmers you must be even smarter.
A goal-oriented product roadmap is an agile planning tool that can help project leaders shift the conversation from tactical to strategic — from detailing features to agreeing on objectives and aligning stakeholders. Features are still provided, of course, but they are derived from the goals, which are measurable, not fuzzy.
What’s the quickest way to do a project? Do it right. And contrary to a popular backlash, processes can help. The key is understanding what process is necessary for the work at hand, and determining how it should evolve as things change. It’s not about bureaucracy, it’s about meeting the needs of your project.
Project teams will always feel pressure to reflect changes in stakeholders’ needs by expanding the scope of products being developed. Rather than resist these changes, anticipate and manage them. Here are three more tips for managing product scope changes, including visualization models and transparent decision-making.
Changes to scope are inevitable, but they aren’t created equal. Good scope changes occur as you discover requirements that serve project goals and align to product vision. Here are three tips for systematically managing product scope with an understanding of business, customer and technical value considerations.
The best way to improve project outcomes is to improve requirements analysis. But as programs grow increasingly complex, organizations must go beyond methodologies to develop and broaden the capabilities of their requirements analysts, starting with these 10 skills.
Many project teams shy away from incorporating use cases into their Agile approaches because they resemble the non-Agile techniques of elicitation and analysis. But there are golden opportunities to leverage the power of use cases with user stories when developing Agile requirements. Let’s look at when and how.
Page: 1 2 3 4 5 6 7 8 9 <prev | next>
|
"Education is an admirable thing. But it is well to remember from time to time that nothing that is worth knowing can be taught." - Oscar Wilde |
