Submit your article about Project Planning or Project Monitoring & Control for next month's Demix Update Issue.
Congratulations to Diane Mizukami (Williams) who had most views for her December 2017 article entitled DAR: Appraisal is Coming,...No Trade Studies Anywhere,...Now What?
Articles - RD / REQM
*Requirements Development / Requirements Management
Article: (RD/REQM) Inter Relationships between Requirements Management and Requirements Development by Hitesh Sanghavi
https://seir.sei.cmu.edu - Article Dated: 7 February 2005 Legend: RM: Requirements Management RD: Requirements Development Difference in objectives of RM and RD: The purpose of RM is to “manage” the requirements of the project's products and product components whereas that of RD is to “produce” customer, product, and product component requirements. RM identifies inconsistencies between requirements and project's plans/work products, whereas RD analyzes the customer, product and product component requirements
Article: (REQM) Managing “Size Creep” in Software Development Projects by Robert D. Leinen Jr. Specialist Master, Deloitte Consulting LLP
https://seir.sei.cmu.edu - Introduction Over the last 30 to 40 years the software industry grown from small entrepreneurial ventures to an enormous entity that in one form or another plays a critical role to most businesses today. As the software industry has grown so has the need to improve and mature capabilities for developing quality software products and solutions. Consequently, there has been a lot of investment focused on perfecting methodologies and tools for managing projects and developing quality software, and the seemingly unending search for the holy grail of estimation. And although there are many identifiable risks to software projects (e.g., inadequate processes, poor quality, unclear goals and objectives, poorly defined requirements, unstable objectives/requirements, inadequate stakeholder involvement, etc.) that the innovations in tools and methodologies seek to address, there are hidden and less recognizable sources of risk which can persist unnoticed . Sometime these hidden risks are quite complex and very difficult to identify, even in situations where they have materialized and created issues for a project.
Article: (REQM) THE EFFECT OF THE IMPLEMENTATION OF CMMI® ON SOFTWARE REQUIREMENTS CHANGE MANAGEMENT by LAWRENCE A. MANTRONE
https://seir.sei.cmu.edu - Abstract
This thesis is intended to describe the changes in requirements change management processes by an organization’s software development team after the organization has successfully implemented a staged implementation of the Software Engineering Institute’s Capability Maturity Model Integration® (CMMI®) for software development. Such implementations are undertaken by organizations for a variety of reasons that generally include a desire to increase efficiency and predictability in software development endeavors. Model implementation calls for an integrated, staged approach of evaluating current software development practices employed by the organization and comparing them to the collection of industry best practices encapsulated in the model.
Presentation: (REQM) What's the Use ( Case) ? by Huet Landry & Scott Schmitz https://seir.sei.cmu.edu - Hello, I’m Huet Landry, the token “Dumb Cajun” for this conference, and this smart-looking guy over here is Scott Schmitz – he can tell you all about the fancy tools. - I’ve spent the last nine years working with a number of different teams in a large government IT department, introducing various improvements in the requirements, design, and testing areas. - Scott has been helping me solve some sticky tool issues for the last year, and is here to help demonstrate the implementation of this approach with Rational Requirements Composer and RequisitePro.
Presentation: (REQM) Requirements Management on the Cheap by John A. Downs, Prepared for the SEPG Conference February, 2002
https://seir.sei.cmu.edu - Problems with Starting the Requirements Management Process • Software engineers do not know how (or like) to write or manage requirements documents • Getting engineers to track changing requirements may be the straw that breaks the camelís back • Commercially available tools are expensive and require a discipline that may not be available when starting up the process • The organization may not be able to provide effective requirements management training, validation, or motivation to software projects due to resource limitations
The purpose of Requirements Management (REQM) is to manage requirements of products and product components of the project and to ensure the management of requirements with the project plans. Requirements Management (REQM) process area is available at CMMI Maturity Level 2 under the Project Management category.
Requirements Management (REQM) helps in better understanding of the requirements, obtaining commitment to requirements, managing requirements changes and ensuring alignment between project work and requirements.
Article: (CMMI) Which CMMI® Institute Model Will Take Your Organization to the Next Level? by CMMI Institute
www.cmmiinstitute.com - Discover Which CMMI® Institute Model Will Take Your Organization to the Next Level!
CMMI Institute models help identify and improve the key capabilities that elevate your organization's performance, quality, and profitability. Many times in business, the problem or solution is not so obvious. With proven best practices, CMMI Institute models allow you to see how your organization's existing processes measure up and where performance improvements are needed. The result?