The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management

Book description:

When software development teams move to agile methods, experienced project managers often struggle -- doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not "command and control."

The authors begin by explaining how agile works: how it differs from traditional "plan-driven" methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute's classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile -- covering the emotional challenges, personal values, and key leadership trait...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software project management methods and approaches Five steps to fostering better software tester and QA results How software testers can get deliverables without nagging Tasktop brings task management into the application lifecycle Software expert on Agile's rise, avoiding project management mistakes Ways software project managers can cope with recessionary trends James Bach interview: Dispelling software testing myths How to improve software project requirements estimates tutorial The QA team's role in application performance evaluation and management 5 ways to answer executives' unfair software test, QA questions Adaptation in project management through agile Software quality management VisibleThread aims to boost IT documentation quality, improve processes Winning responses to "Why is QA always the bottleneck?" Using virtual lab management tools to stop developer, QA conflicts VMLogix LabManager adds support for vSphere 4, Hyper-V R2 Surgient 7's self-provisioning promises software testers quick IT resource access Transitioning from AJAX to .NET what changes to expect in RIA's The QA team's role in application performance evaluation and management Adaptation in project management through agile Budget-friendly Web app performance testing, monitoring tips New requirements definition tools focus on chronic flaws Software requirements management How to improve software project requirements estimates tutorial Expert shows seven ways to improve your project management abilities Five roles test managers play in agile development: Tutorial, part one Quality assurance (QA) and testing's role in requirements Defining requirements during software project feasibility analysis How to avoid requirements creep Software development lifecycle (SDLC) trends 2009: Requirements, agile Is a requirements freeze in a software project a bad idea? Top 10 software requirements tips Seven Steps to Mastering Business Analysis, Ch. 1

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary collaboration diagram  (SearchSoftwareQuality.com) Gantt chart  (SearchSoftwareQuality.com) PERT chart  (SearchSoftwareQuality.com) rapid application development  (SearchSoftwareQuality.com) Software Process Improvement and Capability dEtermination  (SearchSoftwareQuality.com) work breakdown structure  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

s you'll need to succeed.

Coverage includes:

• Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences.



• Understanding the role and value of agile techniques such as iteration/release planning and retrospectives.



• Using agile techniques to systematically and continually reduce risk.



• Implementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvement.



• Learning to trust your teams and listen for their discoveries.



• Procuring, purchasing, and contracting for software in agile, collaborative environments.



• Avoiding the common mistakes software teams make in transitioning to agile.



• Coordinating with project management offices and non-agile teams.



• "Selling" agile within your teams and throughout your organization.

>> Read Chapter 5: Scope Management.

>> Buy the book