Knowledge Reuse in Configuration of Project Management Information Systems: A Change Management Case Study
|
|
- Louisa Morrison
- 7 years ago
- Views:
Transcription
1 Knowledge Reuse in Configuration of Project Management Information Systems: A Change Management Case Study S. Bērziša and J. Grabis Riga Technical University, Faculty of Computer Science and Information Technology, Riga, Latvia berzisa@gmail.com, grabis@iti.rtu.lv Abstract Project management information system is one of main enablers of successful project management. The configuration of the project management information system should be adapted to needs and requirements of a particular project. However, project managers are not always aware of the most appropriate configuration. Adequate knowledge would help the project managers during definition of the configuration requirements. Therefore, an approach for the project management knowledge reuse during configuration of the project management information system is elaborated. This paper presents the case study of application of knowledge reuse in configuration of project change management module. The case study discusses both knowledge acquisition and knowledge utilization processes. I. INTRODUCTION Project management (PM) is knowledge-centric and experience-driven activity [1] supported by an appropriate project management information system (PMIS) [2]. Quality of PMIS affects PM and project success [3] as well as user acceptance and usage of PMIS [4]. Similarly as in the case of enterprise applications when best practices are used in systems configuration [5] [6], utilization of PM knowledge can greatly enhance quality of PMIS. Therefore, an approach for knowledge-based configuration of PMIS is developed in [7]. This approach uses principles of case-based reasoning (CBR) [8] and ensures collection and reuse of theoretical and empirical knowledge. CBR has found multiple applications in PM including project planning [1], [9], software development project effort estimation [10] and construction schedule generation and evaluation [11]. These applications focus on supporting execution of particular PM activities. This paper explores application of knowledge-based configuration and CBR to derive recommendations for setting-up the overall PM environment by configuring PMIS. This application can be perceived as application of CBR to derive best-practices for configuration of packaged software. CBR-based knowledge reuse is expected to assist selection of appropriate configuration of PMIS and to improve correspondence between PMIS s capabilities and PM requirements. A knowledge reuse case analyzed in this paper focuses on configuring the project change management (PCM) module of PMIS. Empirical data from real-life projects and data from several PM methodologies are used to derive PM and PCM knowledge. Paper is divided into five sections. Section 2 presents approach for the PM knowledge reuse. Knowledge acquisition and PMC knowledge content is summarized in Section 3. Section 4 describes case study of PCM configuration definition using accumulated knowledge. Conclusions and recommendations for future research are presented in Section 5. II. APPROACH FOR KNOWLEDGE REUSE The aim of knowledge reuse is to provide knowledge necessary for configuration of PMIS. It is assumed that PMIS is set-up for each new project. Configuration of PMIS is defined as either automated or manual setup of packaged software according to requirements of the particular project. The requirements are specified in a standardized manner as prescribed by XML schema for Configuration of Project Management information systems (XCPM) [12]. XCPM provides means for describing all data items, processes and knowledge areas relevant to the PM domain. The knowledge reuse process (Figure 1) is divided in two sub-processes: knowledge acquisition and knowledge utilization. Knowledge is classified as either theoretical (i.e., derived from PM methodologies) or empirical (i.e., derived from real-life projects). Each case (corresponding to either PM methodologies or real-life projects) is formally described using XCPM and is categorized according to a set of project characteristics (see Section III). The formalized and categorized cases are stored in the knowledge repository. A new case is initialized upon starting a new project. PMIS requirements are defined for the new project and the new case is categorized. Similar cases are searched in the repository by comparing their characteristics with those of the new case, and a list of similar cases is retrieved. Statistical analysis of the similar cases is performed, and a summary of results is displayed to a project manager. The project manager uses the summary and the requirements to prepare the configuration file in the format defined by XCPM. The configuration file is loaded into PMIS, and a fully functional PMIS is obtained. PMIS is configured taking into account previous experience and requirements of the current project. III. KNOWLEDGE ACQUISITION Both theoretical and empirical knowledge is stored in the PM knowledge repository. Theoretical knowledge is collected from standards, methodologies and best practices. This knowledge is
2 Figure 1. Knowledge acquisition and utilization process described once and stored. One case (H i ) is created for each methodology or standard. Empirical knowledge is collected from previously completed projects. Each case describes the configuration of PMIS used for a given project. The case description (C j ) is added to the knowledge repository after it is used in configuration of PMIS. In the case of the PCM configuration, main information elements are work items, attributes of work items and workflows describing status changes of the work items. Views, reports, templates and other information also could be included in the PCM configuration knowledge. A. Theoretical Change Management Knowledge Theoretical knowledge about PCM has been acquired from methodologies and best practices. It has been collected from general and software development specific PM methodologies. PMBOK [2] defines five types of work items related to PCM: actions, change requests, defect, preventive actions and corrective actions. Requests for change, off-specifications, questions, actions and work packages are used in PRINCE2 [13]. SCRUM [14] defines product backlog items, sprint backlog items and bugs. Change requests, issues and actions are defined in [15]. From the area of software development, MSF [16] and RUP [17] and best practices described in [18] have been considered. MSF for Agile Software Development (MSF-ASD) [19] uses bugs, scenarios and tasks for PCM. MSF for CMMI Process Improvement (MSF-CMMI) [20] uses bugs, change requests, issues, requirements and tasks. Business cases, change requests, software requirements, tasks and activities are defined in RUP. Best IT practice described in [18] also defines change requests, issues and tasks. A specific kind of theoretical knowledge is default configurations provided by PM software packages. These configurations could be related with methodology, but not always. Three methodology related process templates are included in Visual Studio Team Foundation Server (VSTFS): MSF-ASD, MSF-CMMI and Visual Studio SCRUM (VS-SCRUM). VS-SCRUM uses product backlog items, bugs, tasks and sprints for PCM [21]. MSF-ASD defines the following types of work items: user stories, tasks, bugs and issues [22]. MSF-CMMI defines the following types of work items for PCM: requirements, tasks, bugs, change requests and issues [23]. Project task management tool JIRA [24], which is geared towards agile software development, uses the following default types of work items: bug, improvement, new feature, task and custom issue. B. Empirical Change Management Knowledge Empirical knowledge about PCM is derived from configurations used in real-life projects. Information about 37 information technology projects in Latvia is collected in the knowledge repository. Statistics about categorization of the empirical projects is summarized in Table I. IV. CASE STUDY An outsourcing software development project for the governmental institution has been chosen as a case for analyzing PCM configuration. The project is carried out by a large IT company. JIRA [24] is used as a project task and change management tool. Historically, various tools for PMC have been used in the development company, but gradually JIRA is being implemented in all projects. The company s own JIRA configuration usually is used for new projects. Originally, this configuration was developed for the internal project using SCRUM [14] methodology. Project managers can prepare their own project configurations, but most of them choose the simplest option of using the default JIRA configuration and having project specific PCM to adapt to it. This option was also used by the project manager of the reviewed case. Description of the case PCM configuration is shown on left side of Figure 2. Five work items or ticket types are included in the default PCM JIRA configuration.
3 TABLE I. CHARACTERISTICS OF EMPIRICAL PROJECTS Characteristic Values and frequency (%) Project type: Outsourcing (49%) In-house (51%) Client: Government (41%) Private (51%) Commercial (8%) Project action: Development (49%) Improvement/maintenance (19%) Implementation (19%) Implementation/development (14%) Project product: Software (100%) Area: IT (100%) Complexity: Mono-discipline (86%) Multi-discipline (14%) Team size: <7 (76%) >=7 (24%) Budget (EUR): < (24%) (49%) (8%) (8%) > (11%) Duration: < 6 months (49%) 6 months year (35%) Year - 2 years (5%) > 2 years (11%) Project organization. structure: Project organization area: Management methodologies (one project can use more than one methodology): Project (65%) Matrix (27%) Functional (5%) Individual (3%) IT (68%) Government (11%) Other (21%) MSF (3%) PMBOK (3%) CMMI (8%) ITIL (11%) SCRUM (8%) ISO 9001:2008 (46%) RUP (3%) Other (11%) None (38%) PM life cycle: Waterfall (57%) Evolutionary (16%) Iterative (11%) Agile (11%) Spiral (3%) V-model (3%) Attributes (i.e., PMIS s data fields) of the work items and status workflows are identical for all work items. The objective of the case study is to use the knowledge repository to identify other alternative configurations of PMIS what could be better suited for the particular project judging by analogy with previously completed projects. PM knowledge reuse is organized in four phases as shown in the knowledge utilization lane in Figure 1. A new case is categorized according to the project characteristics in the first phase (Table II). Similar cases are searched according to equality between project characteristics although only a subset of characteristics is used to determine similarity (the subset is chosen by the project manager). In this case, the empirical cases are compared according to the following characteristics: action, product, methodology and PM life cycle. Similarity of the theoretical cases is evaluated only according to methodology and PM life cycle. Given that the methodology characteristic is not defined for the new case (Table II), this characteristic is ignored in search for similar cases. The search for similar cases results in ten similar empirical cases and eight relevant theoretical cases: PMBOK, PRINCE2, MSF-CMMI, RUP, the best practices [15] and [18], VSTFS MSF-CMMI and JIRA default configuration. In the third phase, the retrieved similar cases are analyzed and PMIS configuration suggestions for the project manager are generated. These suggestions are presented in three steps: 1) types of PCM work items types are established; 2) attributes for each type of work items are defined; and 3) a workflow for each type of work items is defined. A. Types of Work Item Types of work items have been identified from eighteen similar cases, and they observation frequency is calculated. As the result, the project manager gets information shown in Table III. The most frequently observed types of work items are change request (83%), task (67%), issue (56%) and bug (33%). These four types are included in the proposed PCM configuration. Change requests and issues are registered by the client, but tasks and bugs are used by the project team Project type: Client: TABLE II. CHARACTERISTICS OF THE NEW CASE Project action: Characteristic Project product: Area: Complexity: Value Outsourcing Government Development Software IT Multi-discipline Team size: >=7 Project budget: > Duration: Project organization structure: Organization work area: Year - 2 years Project Methodologies: - PM life cycle: TABLE III. LIST OF TYPES OF WORK ITEMS IT Waterfall Work item type Frequency (%) Change request 83% Task 67% Issue 56% Bug 33% Action 17% Question 17% New feature 17% Requirement 11% Improvement 11% Defect 6% Preventive action 6% Corrective action 6% Off-specification 6% Work package 6% Activity 6% Business Case 6% Software requirement 6%
4 B. Attributes of Work Items Attributes or data fields should be defined for each of the selected types of work items. For the each work item the list of attributes is created by analyzing the attributes of work items in descriptions of the similar cases. In this case study change request is described in 15 cases, task - 12, issue - 10 and bug 6. The result of analysis is shown in Table IV. This table shows only attributes whose observation frequency is larger than 20% for at least one type of work items. The project manager gets this information separately for each type of work items as he/she specifies the configuration of PMIS. Attributes with different names might have identical semantic meaning. For example, a person submitting the TABLE IV. ATTRIBUTES OF WORK ITEMS Frequency (%) Change Issue Task Bug Attributes request Key/id 100% 100% 100% 100% Summary/Title 87% % 100% Type 0% 40% 100% 50% Status/State/Err status 100% 100% 100% 100% Priority 100% 100% 100% 100% Resolution 67% 100% 100% 50% Affects Version(s)/ 47% 50% 75% 67% Found in Fix Version(s)/ 67% 80% 100% 83% Iteration Component(s)/Area/ 60% 70% 92% 100% System/Block Labels(s)/Keywords 33% 30% 58% 50% Environment 33% 30% 58% 50% Description 100% 100% 100% 100% Assignee/Assigned 73% 100% 100% 100% to/addressed Reporter/Created 100% 100% 100% 100% by/author/initiator Due date 47% 60% 75% 50% Created/ Created date 100% 100% 100% 100% Updated/Change date 100% 80% 100% 83% Resolved/Resolved 53% 60% 83% 83% date Estimate 73% 50% 100% 67% Remaining 60% 30% 83% 67% Logged/Completed 47% 40% 62% 67% Comment 47% 40% 67% 67% Fix in build/ Fix/ 0% 0% 8% 50% Build(fix) Security level 7% 10% 33% 67% History 27% 40% 33% 100% Closed date 20% 40% 25% 50% Attachment 47% 70% 92% 100% Links 27% 40% 33% 83% Triangle 20% 30% 25% 19% Blocked 20% 0% 25% 19% Changed by 20% 30% 25% 19% Close by 20% 30% 25% 19% Escape 0% 30% 0% 0% Resolved by 20% 30% 8% 19% Impact assessment 33% 20% 0% 0% change request could be called as reporter, created by, author, initiator and so on. The synonym dictionary is used to identify semantically equal attributes. This dictionary allows users to list name with equal meanings and to use this list in summarizing attribute of the work item. The resulting lists of attributes are similar for all four types of work items with some minor deviations. For example, the impact assessment is only used in the change request. C. Workflows Workflows are also defined for each type of work items, but workflow comparison is not as simple as comparison of attributes because processes can be describe in different ways. However, in the PCM case, it is possible to analyze the statuses and transactions changing status value just like the attributes. Results of the workflow statuses analysis are shown in Table V. Different lists of the workflow statuses are used TABLE V. LIST OF WORKFLOW STATUSES Frequency (%) Change Issue Task Bug Workflow statuses request Active 20% 30% 25% 33% Agreed 27% 10% 8% 17% Approved 40% 20% 0% 0% Assigned 20% 20% 8% 0% Canceled 0% 0% 25% 33% Clarification 20% 20% 8% 17% Client testing 20% 0% 25% 17% Client testing done 20% 0% 25% 17% Closed 100% 100% 100% 100% Code review 0% 0% 8% 17% Delivered 20% 0% 25% 17% Deployment 20% 20% 17% 0% Duplicated 7% 0% 0% 0% Evolution 7% 10% 0% 0% Feedback 7% 10% 8% 0% In progress 13% 30% 42% 50% New 7% 10% 17% 0% On hold 27% 0% 25% 17% Open 47% 50% 33% 50% Production 20% 0% 25% 17% Proposed 20% 30% 25% 33% Ready for review 0% 0% 8% 17% Ready for testing 27% 10% 42% 33% Realize 47% 30% 33% 17% Registered 20% 0% 0% 17% Rejected 13% 10% 8% 0% Reopened 13% 30% 33% 33% Resolved 47% 60% 58% 83% Submitted 7% 0% 0% 17% Test failed 7% 0% 0% 0% Tested 27% 10% 33% 17% Testing 40% 30% 50% 50% Unassigned 7% 10% 8% 0% Verification 20% 0% 0% 0%
5 for the each type of work items, but all include the following statuses: open, testing, resolved and closed. Like with the list of attributes of work items, this information is shown separately about each type of work items when the project manager describes the workflow of a particular work item. Including only statuses with observation frequency more than 20%, the workflow for change request includes the following statuses: agreed, approved, closed, on hold, open, ready for testing, realize, resolved, tested and testing. If multiple similar statuses are suggested for inclusion in the workflow (e.g., agreed and approved ), the project manger needs to choose only one of these similar statuses. When workflow statuses have been chosen then information about the transactions between these statuses is collected in a similar manner. D. Proposed Configuration of PMIS The proposed knowledge based configuration of PMIS is created including all elements with observation frequency larger than 20%. The types of work items and the corresponding workflows are shown in Figure 2 and the attributes of work items are listed in Table IV. Comparison of the initial configuration with the proposed configuration shows that only two work items have been kept task and bug. Also two new types of work items have been added change request and issue. Most of the attributes of work items have not been changed. Majority of differences occur in compassion of workflows. A separate workflow has been established for each type of work items, and all four workflows obtained differ from the original workflow. The proposed configuration of PMIS is more suitable Figure 2. PCM configurations
6 for the reviewed waterfall project than the original configuration, because it has been created using knowledge from the waterfall project cases. It could be considered as a draft configuration, which is refined by the project manager according to project requirements and needs before actually loading it into PMIS. V. CONCLUSIONS This paper presents application of PM knowledge during configuration of PMIS. This approach includes the knowledge acquisition and utilization processes. The case of configuring PCM module of PMIS is used to demonstrate application of the approach. The result of the PCM case analysis is the configuration of PMIS that includes four types of work items, their attributes and also different workflows for the each type of work items. This configuration has been created by including all suggestions with observation frequency more than 20%. The final configuration to be loaded into PMIS is manually refined by the project manager who can choose to accept or reject these suggestions as well as to add additional information. This way knowledge about previously completed projects and PM methodologies complements needs and requirements of a particular project to develop an appropriate configuration of PMIS. Two problems of knowledge reuse have been identified in the case study. The first problem is that different names are used for semantically equivalent work items, attributes or statuses. Without analyzing and merging of these synonym names, the result of statistical analysis would be incorrect. The synonym dictionary is used as a solution of this problem. The second problem is related to analyzing workflow data. The description of PM workflows is not standardized and therefore simple comparison and analysis of their data is impossible. In the PCM case, the workflows are defined using only statuses and transactions, and, therefore, frequency data can be used. However, this approach would not yield sufficient result in case of sequential workflows. Identification of workflow similarity is one of the main topics for future research. Evaluation of efficiency of configurations obtained as the result of knowledge reuse is another important issue to be addressed. ACKNOWLEDGMENT This work has been supported by the European Social Fund within the project Support for the implementation of doctoral studies at Riga Technical University. REFERENCES [1] H.-L. Yang and C.-S. Wang, Recommender system for software project planning one application of revised CBR algorithm, Expert Systems with Applications, vol. 36, pp July [2] Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fourth Edition, Project Management Institute, [3] L. Raymond and F. Bergeron, Project management information systems: An empirical study of their impact on project managers and project success, International Journal of Project Management, vol. 26, pp , February [4] A.S.B. Ali, F.T. Anbari, and W.H. Money, Impact of organizational and project factors on acceptance and usage of project management software and perceived project success Project Management Journal, vol. 39, pp. 5 33, June [5] Y. Li, X.W. Liao, and H.Z. Lei, A knowledge management system for ERP implementation, Systems Research and Behavioral Science, vol. 168, pp , March [6] R. Vandaie, The role of organizational knowledge management in successful ERP implementation projects, Knowledge-Based Systems, vol. 21, pp , December [7] S. Bērziša and J. Grabis, A framework for knowledge-based configuration of project management information systems,, Information Technologies Proceedings of the International Conference on Information and Software Technologies, R. Butleris and R. Butkiene, eds., Kaunas: Kaunas University of Technology, 2011, pp [8] A. Aamodt and E. Plaza, Case-based reasoning: Foundational issues, methodological variations, and system approaches, AI communications, vol. 7, pp , March [9] J. Lee and N. Lee, Least modification principle for case-based reasoning: a software project planning experience, Expert Systems with Applications, vol. 30, pp , Febuary [10] R.J. Aarts, A CBR architecture for project knowledge management, Advences in Case-Based Reasoning, Smyth, P, eds., 1998, pp [11] E. Mikulakova, M. Konig, E. Tauscher, and K. Beucke, Knowledge-based schedule generation and evaluation, Advanced Engineering Informatics, vol. 24, pp , November [12] S. Bērziša, XML-based Specification of the Project Management Domain and Its Application, Databases and Information Systems VI. Volume 224 Frontiers in Artificial Intelligence and Applications, J. Barzdins and M. Kirikova, eds., Amsterdam: IOS Press, 2011, pp [13] B. Hedeman, G.V.V. Heemst, and H. Fredriksz, Project Management Based on PRINCE2 (Best Practice), Van Haren Publishing, [14] K. Schwaber, Agile Project Management with Scrum, Microsoft Press, [15] J. Charvat, Project Management Methodologies: Selecting, Implementing, and Supporting Methodologies and Processes for Projects, Wiley, 2003 [16] M.S.V. Turner, Microsoft Solutions Framework Essentials: Building Successful Technology Solutions, Microsoft Press, [17] R.D. Gibbs, Project Management with the IBM(R) Rational Unified Process(R): Lessons From The Trenches, IBM Press, [18] K. Bainey, Integrated It Project Management: A Model-Centric Approach, Artech House Publishers, [19] Microsoft, MSF for Agile Software Development Process Guidance F3EA426-C2B BA0F-35A021D85234&displaylang=en, [20] Microsoft, MSF for CMMI Process Improvement, 0B578F1-B7A4-459F-A783-04BC82CB2359, [21] MSDN, Visual studio SCRUM [22] MSDN, MSF for Agile Software Development [23] MSDN, MSF for CMMI Process Improvement, [24] Atlassian,
Project Phase Dependent Configuration of Project Management Information Systems
doi: 10.2478/v10313-012-0011-x Project Phase Dependent Configuration of Project Management Information Systems Solvita Berzisa 1, Janis Grabis 2, 1-2 Riga Technical University Abstract Project management
More information11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
More informationAPPLYING CASE BASED REASONING IN AGILE SOFTWARE DEVELOPMENT
APPLYING CASE BASED REASONING IN AGILE SOFTWARE DEVELOPMENT AIMAN TURANI Associate Prof., Faculty of computer science and Engineering, TAIBAH University, Medina, KSA E-mail: aimanturani@hotmail.com ABSTRACT
More informationSurveying and evaluating tools for managing processes for software intensive systems
Master Thesis in Software Engineering 30 Credits, Advanced Level Surveying and evaluating tools for managing processes for software intensive systems Anuradha Suryadevara IDT Mälardalen University, ABB
More informationRedesigned Framework and Approach for IT Project Management
Vol. 5 No. 3, July, 2011 Redesigned Framework and Approach for IT Project Management Champa Hewagamage 1, K. P. Hewagamage 2 1 Department of Information Technology, Faculty of Management Studies and Commerce,
More informationTRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
More informationAgile SW Development @ Siemens
CON ECT INFORMUNITY, 24.3.2014 Agile SW Development @ Siemens Corporate Development Center Unrestricted Siemens Aktiengesellschaft Österreich 2013 All rights reserved. Eva Kišo ová - that s me Faculty
More informationCS4507 Advanced Software Engineering
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
More informationSoftware Engineering
1 Software Engineering Lecture 2: Software Life Cycles Stefan Hallerstede Århus School of Engineering 25 August 2011 2 Contents Naive Software Development Code & Fix Towards A Software Process Software
More informationMANUAL TESTING. (Complete Package) We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info
MANUAL TESTING (Complete Package) WEB APP TESTING DB TESTING MOBILE APP TESTING We are ready to serve Latest Testing Trends, Are you ready to learn.?? New Batches Info START DATE : TIMINGS : DURATION :
More informationContents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
More informationAgile SW Development @ Siemens
CON ECT INFORMUNITY, 19.9.2013 Neue Software-Trends Agilität Prozesse & RE Agile SW Development @ Siemens Corporate Development Center Dr. Kurt Hofmann > 25 years Siemens ACT SW developer at PSE Team leader
More informationModels of Software Development
October 28, 2015 Verification & Validation In many computer science courses, software is submitted once, graded, and thrown away. In real life, software development is an process. Some attempts to codify
More informationManaging Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
More informationSoftware Development Process
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
More informationMKS Integrity & CMMI. July, 2007
& CMMI July, 2007 Why the drive for CMMI? Missed commitments Spiralling costs Late delivery to the market Last minute crunches Inadequate management visibility Too many surprises Quality problems Customer
More informationBest Overall Use of Technology. Jaspersoft
Best Overall Use of Technology Jaspersoft Kerstin Klein Manager, Engineering Processes/ Infrastructure, Jaspersoft From requirements to release QA centric development From Requirement to Release QA-Centric
More informationSoftware Life Cycles and Configuration Management
Theory Lecture Plan 2 Software Configuration Lecture 11 Software Engineering TDDC88/TDDC93 autumn 2008 Department of Computer and Information Science Linköping University, Sweden L1 - Course Introduction
More informationApplication Lifecycle Management Using Visual Studio 2013 (SCRUM)
Course Code: QAALMS13 Vendor: Microsoft Course Overview Duration: 3 RRP: 2,009 Application Lifecycle Management Using Visual Studio 2013 (SCRUM) Overview This three-day, instructor-led course provides
More informationAB Suite in the Application Lifecycle
AB Suite in the Application Lifecycle By: Alan Hood White Paper The application lifecycle goes well beyond simply writing applications and testing them. It includes everything from the initial collection
More informationDemand & Requirements Management Software Development QA & Test Management IT Operations & DevOps Change Management Agile, SAFe, Waterfall Support
Demand & Requirements Management Software Development QA & Test Management IT Operations & DevOps Change Management Agile, SAFe, Waterfall Support Workflows with Business Process Management capabilities
More informationMicrosoft Change Management Applying Comparison of Different Versions
Acta Technica Jaurinensis Vol. 7., No.2., pp. 183-192, 2014 DOI: 10.14513/actatechjaur.v7.n2.282 Available online at acta.sze.hu Microsoft Change Management Applying Comparison of Different Versions I.
More information44-76 mix 2. Exam Code:MB5-705. Exam Name: Managing Microsoft Dynamics Implementations Exam
44-76 mix 2 Number: MB5-705 Passing Score: 800 Time Limit: 120 min File Version: 22.5 http://www.gratisexam.com/ Exam Code:MB5-705 Exam Name: Managing Microsoft Dynamics Implementations Exam Exam A QUESTION
More informationYou Want to Use Scrum, You are Told to Use CMMI
You Want to Use Scrum, You are Told to Use CMMI How They can Work Together Elegantly and Both Provide Benefit Neil Potter The Process Group neil@processgroup.com 1 Agenda Summary of Scrum and CMMI Approach
More informationEffective Team Development Using Microsoft Visual Studio Team System
Effective Team Development Using Microsoft Visual Studio Team System Course 6214A: Three days; Instructor-Led Introduction This three-day instructor-led course provides students with the knowledge and
More informationJOB DESCRIPTION APPLICATION LEAD
JOB DESCRIPTION APPLICATION LEAD The Application Lead will provide functional support and to expand capabilities in the area of systems configuration. This function provides the initial step in the process
More informationSoftware Quality Development and Assurance in RUP, MSF and XP - A Comparative Study
Software Quality Development and Assurance in RUP, MSF and XP - A Comparative Study Wolfgang Zuser Vienna University of Technology wolfgang.zuser@inso.tuwien.ac.at Stefan Heil Capgemini Consulting Austria
More informationCase Study on Critical Success Factors of Running Scrum *
Journal of Software Engineering and Applications, 2013, 6, 59-64 http://dx.doi.org/10.4236/jsea.2013.62010 Published Online February 2013 (http://www.scirp.org/journal/jsea) 59 Case Study on Critical Success
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More informationA Case Retrieval Method for Knowledge-Based Software Process Tailoring Using Structural Similarity
A Case Retrieval Method for Knowledge-Based Software Process Tailoring Using Structural Similarity Dongwon Kang 1, In-Gwon Song 1, Seunghun Park 1, Doo-Hwan Bae 1, Hoon-Kyu Kim 2, and Nobok Lee 2 1 Department
More informationTruly Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination)
Truly Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Neil Potter The Process Group Lead Appraiser / Improvement Coach Organization
More informationWaterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationTo introduce software process models To describe three generic process models and when they may be used
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationThe Design and Improvement of a Software Project Management System Based on CMMI
Intelligent Information Management, 2012, 4, 330-337 http://dx.doi.org/10.4236/iim.2012.46037 Published Online November 2012 (http://www.scirp.org/journal/iim) The Design and Improvement of a Software
More informationSoftware Engineering Reference Framework
Software Engineering Reference Framework Michel Chaudron, Jan Friso Groote, Kees van Hee, Kees Hemerik, Lou Somers, Tom Verhoeff. Department of Mathematics and Computer Science Eindhoven University of
More informationThe Agile PMO. Contents. Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404
The Agile PMO Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc. 4100 E. Third Avenue, Suite 205 Foster City, CA 94404 Kevin.thompson@cprime.com Abstract The development of Agile processes
More informationApplication of software product quality international standards through software development life cycle
Central Page 284 of 296 Application of software product quality international standards through software development life cycle Mladen Hosni, Valentina Kirinić Faculty of Organization and Informatics University
More informationIBM Maximo Asset Management IBM Tivoli Asset Management for IT IBM Tivoli Service Request Manager. Version 7.1. Workflow Implementation Guide
IBM Maximo Asset Management IBM Tivoli Asset Management for IT IBM Tivoli Service Request Manager Version 7.1 Workflow Implementation Guide Note Before using this information and the product it supports,
More informationOrthogonal Defect Classification in Agile Development
Orthogonal Defect Classification in Agile Development Monika Jagia, IBM Software Group India, monika.jagia@in.ibm.com Seema Meena, IBM Software Group India, seemeena@in.ibm.com 2008 IBM Corporation Copyright
More informationG-Cloud Service Definition. Atos Business Intelligence Dashboards and Analytics SCS
G-Cloud Service Definition Atos Business Intelligence Dashboards and Analytics SCS Atos Business Intelligence Dashboards and Analytics SCS The Atos approach to Business Intelligence (BI) Dashboards and
More informationAn introduction to the benefits of Application Lifecycle Management
An introduction to the benefits of Application Lifecycle Management IKAN ALM increases team productivity, improves application quality, lowers the costs and speeds up the time-to-market of the entire application
More informationSinghania University, Jhunjhunu, Rajasthan, India. 2 Department of Information Technology King Abdul Aziz University, Jeddah, Saudi Arabia
www.ijcsi.org 441 A Comprehensive Study of Commonly Practiced Heavy and Light Weight Software Methodologies 1 Asif Irshad Khan, 2 Rizwan Jameel Qurashi and 3 Usman Ali Khan 1 Department of Computer Science
More informationAgile Based Software Development Model : Benefits & Challenges
Agile Based Software Development Model : Benefits & Challenges Tajinder Kumar Assistant Professor, IT Department JMIT Radaur, Haryana Vipul Gupta Assistant Professor, IT Department JMIT Radaur, Haryana
More informationBest-Practice Software Engineering: Software Processes to Support Project Success. Dietmar Winkler
Best-Practice Software Engineering: Software Processes to Support Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems Dietmar.Winkler@qse.ifs.tuwien.ac.at
More information10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design
Session # 3 Contents Systems Analysis and Design 2 1 Tiers of Software Development 10/4/2013 Information system development project Realistic behavior 3 Information system development project System Development
More informationData Mining Governance for Service Oriented Architecture
Data Mining Governance for Service Oriented Architecture Ali Beklen Software Group IBM Turkey Istanbul, TURKEY alibek@tr.ibm.com Turgay Tugay Bilgin Dept. of Computer Engineering Maltepe University Istanbul,
More informationSustainable Software Development in Agile and CMMI: Apply Lessons Learned today
Sustainable Software Development in Agile and CMMI: Apply Lessons Learned today 2009 What is the CMMI Level 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed 1 Initial Focus Continuous Process
More informationREVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS
REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS Lisana Universitas Surabaya (UBAYA), Raya Kalirungkut, Surabaya, Indonesia E-Mail: lisana@ubaya.ac.id
More informationSystem Development Life Cycle Guide
TEXAS DEPARTMENT OF INFORMATION RESOURCES System Development Life Cycle Guide Version 1.1 30 MAY 2008 Version History This and other Framework Extension tools are available on Framework Web site. Release
More informationCertified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage
More informationThe Software Life Cycle. CSE 308: Software Engineering
The Software Life Cycle CSE 308: Software Engineering 1 Life Cycle Models A software life cycle model represents all of the activities and work products necessary to develop a software system Life cycle
More informationEvaluation of agility in software development company
Evaluation of agility in software development company Gusts Linkevics Riga Technical University, Riga, Latvia, gusts@parks.lv Abstract Organization s and team s experience in agile methodology can be more
More informationCONDIS. IT Service Management and CMDB
CONDIS IT Service and CMDB 2/17 Table of contents 1. Executive Summary... 3 2. ITIL Overview... 4 2.1 How CONDIS supports ITIL processes... 5 2.1.1 Incident... 5 2.1.2 Problem... 5 2.1.3 Configuration...
More informationHow Silk Central brings flexibility to agile development
How Silk Central brings flexibility to agile development The name agile development is perhaps slightly misleading as it is by its very nature, a carefully structured environment of rigorous procedures.
More informationKey Benefits of Microsoft Visual Studio Team System
of Microsoft Visual Studio Team System White Paper November 2007 For the latest information, please see www.microsoft.com/vstudio The information contained in this document represents the current view
More informationSoftware Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
More informationA MODEL FOR RISK MANAGEMENT IN AGILE SOFTWARE DEVELOPMENT
A MODEL FOR RISK MANAGEMENT IN AGILE SOFTWARE DEVELOPMENT Abstract Author Ville Ylimannela Tampere University of Technology ville.ylimannela@tut.fi This paper researches risk management in agile software
More informationThe Dynamics of Project Management
The PROJECT PERFECT White Paper Collection Abstract The Dynamics of Project Management Eric Tse This white paper suggests project management methods and practices can move from a static, unidirectional
More informationTesthouse Training Portfolio
Testhouse Training Portfolio TABLE OF CONTENTS Table of Contents... 1 HP LoadRunner 4 Days... 2 ALM Quality Center 11-2 Days... 7 HP QTP Training Course 2 Days... 10 QTP/ALM Intensive Training Course 4
More informationCopyrighted www.eh1infotech.com +919780265007, 0172-5098107 Address :- EH1-Infotech, SCF 69, Top Floor, Phase 3B-2, Sector 60, Mohali (Chandigarh),
Content of 6 Months Software Testing Training at EH1-Infotech Module 1: Introduction to Software Testing Basics of S/W testing Module 2: SQA Basics Testing introduction and terminology Verification and
More informationCertified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions
More informationAgile Software Engineering, a proposed extension for in-house software development
Journal of Information & Communication Technology Vol. 5, No. 2, (Fall 2011) 61-73 Agile Software Engineering, a proposed extension for in-house software development Muhammad Misbahuddin * Institute of
More informationThe Role of Information Technology Studies in Software Product Quality Improvement
The Role of Information Technology Studies in Software Product Quality Improvement RUDITE CEVERE, Dr.sc.comp., Professor Faculty of Information Technologies SANDRA SPROGE, Dr.sc.ing., Head of Department
More informationNexus Guide. The Definitive Guide to Nexus: The exoskeleton of scaled Scrum development. Developed and sustained by Ken Schwaber and Scrum.
Nexus Guide The Definitive Guide to Nexus: The exoskeleton of scaled Scrum development Developed and sustained by Ken Schwaber and Scrum.org August 2015 Table of Contents Nexus Overview... 2 Purpose of
More informationInformation System Project Management Context (IS PM 2. lecture, 2012)
Information System Project Management Context Topics of the current lecture Overview of IT processes in organization System work framework draft Project life cycle Project management methodologies IT Processes
More informationClassical Software Life Cycle Models
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
More informationIn the IEEE Standard Glossary of Software Engineering Terminology the Software Life Cycle is:
In the IEEE Standard Glossary of Software Engineering Terminology the Software Life Cycle is: The period of time that starts when a software product is conceived and ends when the product is no longer
More informationALM2013VS_ACC: Application Lifecycle Management Using Visual Studio 2013
ALM2013VS_ACC: Application Lifecycle Management Using Visual Studio 2013 Description This three-day, instructor-led course provides students with the knowledge and skills to effectively use the Application
More informationA complete software development process of a general report publication service implemented using Web Services
A complete software development process of a general report publication service implemented using Web Services Anders Nilsson & Klas Fahlberg February 1, 2008 Master s Thesis in Computing Science, 2*30
More informationWhen is Agile the Best Project Management Method? Lana Tylka
When is Agile the Best Project Management Method? Lana Tylka Staged Incremental Deliveries Prototypes Plan Develop Design Deploy Test Maintain Sequential Steps Multiple Iterations Waterfall Sprints, Spirals
More informationMaster Data Management: dos & don ts
Master Data Management: dos & don ts Keesjan van Unen, Ad de Goeij, Sander Swartjes, and Ard van der Staaij Master Data Management (MDM) is high on the agenda for many organizations. At Board level too,
More informationALM Solutions using Visual Studio TFS 2013 ALMI13; 5 Days, Instructor-led
ALM Solutions using Visual Studio TFS 2013 ALMI13; 5 Days, Instructor-led Course Description This five day course is designed to get your entire team working efficiently with Microsoft s Application Lifecycle
More informationWhat is a life cycle model?
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
More informationSAS in clinical trials A relook at project management,
SAS in clinical trials A relook at project management, tools and software engineering Sameera Nandigama - Statistical Programmer PhUSE 2014 AD07 2014 inventiv Health. All rights reserved. Introduction
More informationUsing Use Cases on Agile Projects
Using Use Cases on Agile Projects Ivar Jacobson with Ian Spence Agenda What are agile teams looking for? Cards, conversations, and confirmations Knowing what to do and when it s done Being agile with use
More informationSoftware Quality Assurance in Agile, XP, Waterfall and Spiral A Comparative Study
Software Quality Assurance in Agile, XP, Waterfall and Spiral A Comparative Study S. Vijayakumar vijsy003@students.unisa.edu.au School of Computer and Information Science University of South Australia,
More informationInternational Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research)
International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research) International Journal of Engineering, Business and Enterprise
More informationA Variability Viewpoint for Enterprise Software Systems
2012 Joint Working Conference on Software Architecture & 6th European Conference on Software Architecture A Variability Viewpoint for Enterprise Software Systems Matthias Galster University of Groningen,
More informationAgile in Financial Services A Framework in Focus
Agile in Financial Services A Framework in Focus John B. Hudson, B.Sc, PMP, CSM PMI NJ Chapter February 19, 2013 19 Feb 2013 1 Objectives 1. Agile Development an Overview 2. The Agile Enterprise Infrastructure
More informationMaintaining Quality in Agile Environment
Maintaining Quality in Agile Environment Authors : Mr. Vasu Padmanabhan, Mr. V. Arockia Jerome Presenter / Speaker : Mr. V. Arockia Jerome Banking and Financial Services, Delivery Excellence Group (DEG)
More informationA Capability Maturity Model (CMM)
Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability
More informationDefect Tracking Best Practices
Defect Tracking Best Practices Abstract: Whether an organization is developing a new system or maintaining an existing system, implementing best practices in the defect tracking and management processes
More informationUsing the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects
Transdyne Corporation CMMI Implementations in Small & Medium Organizations Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Dana Roberson Quality Software Engineer NNSA Service
More informationBusiness Analysis From Yes-M Systems LLC Length: Approx 7 weeks/55 hours Audience: Students with or without IT experience or knowledge Student
Business Analysis From Length: Approx 7 weeks/55 hours Audience: Students with or without IT experience or knowledge Student Location To students from around the world Delivery Method: Instructor-Led Live
More informationDemand & Requirements Management Software Development QA & Test Management IT Operations & DevOps Change Management Agile, SAFe, Waterfall Support
Demand & Requirements Management Software Development QA & Test Management IT Operations & DevOps Change Management Agile, SAFe, Waterfall Support Overview codebeamer is a single-repository Application
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 9 Agile Methodologies: Scrum 1 Scrum First mentioned as a development method in 1986, referring to a fast and flexible product development
More informationSoftware Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
More informationSoftware Engineering of NLP-based Computer-assisted Coding Applications
Software Engineering of NLP-based Computer-assisted Coding Applications 1 Software Engineering of NLP-based Computer-assisted Coding Applications by Mark Morsch, MS; Carol Stoyla, BS, CLA; Ronald Sheffer,
More informationFrom Traditional Functional Testing to Enabling Continuous Quality in Mobile App Development
From Traditional Functional Testing to Enabling Continuous Quality in Mobile App Development Introduction Today s developers are under constant pressure to launch killer apps and release enhancements as
More informationWhen User Experience Met Agile: A Case Study
When User Experience Met Agile: A Case Study Michael Budwig User Experience Manager PayPal 2211 North 1 st Street, San Jose, California 95131 USA mbudwig@paypal.com Soojin Jeong Manager, User Interface
More informationProject Management in Software: Origin of Agile
PAGE 1 ios App Development Project Management in Software: Origin of Agile PAGE 2 Learning Outcomes By the end of the unit, you should be able to: 1. Differentiate between Waterfall and Agile process 2.
More informationNeglecting Agile Principles and Practices: A Case Study
Neglecting Agile Principles and Practices: A Case Study Patrícia Vilain Departament de Informatics and Statistics (INE) Federal University of Santa Catarina Florianópolis, Brazil vilain@inf.ufsc.br Alexandre
More informationFamily: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to
Unified Process Family: Iterative Enhancement Origin: Ivar Jacobson, James Rumbaugh, Grady Booch, 1996 Defines process framework that is adaptable to various application domains different organizations
More informationTowards a new approach of continuous process improvement based on CMMI and PMBOK
www.ijcsi.org 160 Towards a new approach of continuous process improvement based on CMMI and PMBOK Yassine Rdiouat 1, Naima Nakabi 2, Khadija Kahtani 3 and Alami Semma 4 1 Department of Mathematics and
More informationGAIA Service Catalogs: A Framework for the Construction of IT Service Catalogs
Revista de Sistemas de Informação da FSMA n. 14 (2014) pp. 11-25 http://www.fsma.edu.br/si/sistemas.html GAIA Service Catalogs: A Framework for the Construction of IT Service Catalogs Luiz Henrique Taconi,
More informationG-Cloud Service Definition. Atos Business Intelligence Dashboards and Analytics SCS
G-Cloud Service Definition Atos Business Intelligence Dashboards and Analytics SCS Atos Business Intelligence Dashboards and Analytics SCS The Atos approach to Business Intelligence (BI) Dashboards and
More informationReaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
More informationBasic Unified Process: A Process for Small and Agile Projects
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
More information