Abstract
Process descriptions represent high-level plans and do not contain information necessary for concrete software development projects. Processes that are unrelated to daily practices or that are hardly mapped to project practices, cause misalignments between processes and projects. We argue that software processes should emerge and evolve collaboratively within an organization. With this propose, this article describes the ProPAM methodology and explores the details of its static view. We also present a case study to validate effectiveness of the proposed methodology. The aim of the case study was to analyse the effects of using ProPAM in a IT organization.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
