PROJECT MANAGEMENT THEORY MEETS PRACTICE
|
|
- Jeremy McKenzie
- 8 years ago
- Views:
Transcription
1 Tove Brink Pekka Buttler Helge Søndergård Hvid Theis von Moos Charles Møller Jan Pries-Heje Eva Riis Vibeke Kristine Scheller Jesper Schlamovitz Nazli Shahim Per Svejvig Gitte Tjørnehøj The book presents a selection of state-of-the-art research, theory and models based on studies of project management practice. Topics include: Self-organizing agile management teams How Scrum influences the temporal environment Hidden goals and what you can do Frontloading your project Metaphors used to communicate in the project Maturity in project-portfolio management Value generation in projects Heroes as catalysts in projects Project Management Theory Meets Practice is published in cooperation with the Danish Project Management Association. ISBN: PROJECT MANAGEMENT THEORY MEETS PRACTICE Andreas Saxkjær Jespersen Project Management Theory Meets Practice contains the proceedings from the 1st Danish Project Management Research Conference (DAPMARC 2015), held in Copenhagen, Denmark, on May 21st, Jan Pries-Heje and Per Svejvig (eds.) AUTHORS Jan Pries-Heje and Per Svejvig (eds.) PROJECT MANAGEMENT THEORY MEETS PRACTICE Jan Pries-Heje is a Full Professor in Information Systems at Roskilde University, Denmark. He is currently head of a research group on IT innovation and head of Studies for Master in Project Management and Process Improvement. Jan holds M.Sc. and Ph.D. degrees from Copenhagen Business School. He has written more than 250 papers and books in International Conferences and Journals. He has studied and written about internet speed projects, agile projects, estimation and risk management, enterprise architecture, IT strategy and maturity. Further, Jan has more than 20 years of experience working as Project and Research manager and doing research in IT and Project Management. For the last 5 years he has been active in the Research Programme of the Danish Project Management Association. Per Svejvig is Associate Professor at the Department of Business Administration, Aarhus University. His research interests are in the areas of project management and outsourcing, implementation and use of enterprise systems, managing IT-enabled change, and interplay between technology and organizations. He has published in International Journal of Project Management, Journal of Information Technology, Scandinavian Journal of Information Systems, Journal of Information Technology Case and Application Research, International Journal of Enterprise Information Systems, International Journal of Business Information Systems, International and Journal of Services Technology and Management. He holds a PhD in Enterprise Systems from Aarhus University. He has more than 25 years of business experience as a manager, project manager and consultant. He is a Certified Senior Project Manager (IPMA level B) and is active in Danish Project Management Association Project Management OMSLAG sort/hvid forfatter 26 MAR.indd 1 14/04/
2 Project Management Theory Meets Practice
3
4 Jan Pries-Heje and Per Svejvig (eds.) Project Management Theory Meets Practice
5 Jan Pries-Heje and Per Svejvig (eds.) Project Management Theory Meets Practice 1. edition 2015 Roskilde University Press 2015 COVER: SL grafik (slgrafik.dk) TYPESET: SL grafik PRINT: Specialtrykkeriet Viborg A/S TRYKT BOG ISBN: E-BOG ISBN: Published in cooperation with the Danish Project Management Association Roskilde University Press Rosenørns Allé Frederiksberg C info@samfundslitteratur.dk samfundslitteratur.dk/ruforlag All rights reserved. No part of this publication may be reproduced or used in any form or by any means graphic, electronic or mechanical including photocopying, recording, taping or information storage or retrieval systems without permission in writing from Roskilde Universitetsforlag.
6 Foreword DAPMARC FOREWORD DAPMARC 2015 This is something special! This book contains the Proceedings for the First Danish Project Management Research Conference (DAPMARC), held in Copenhagen, 21 May It is always exciting to start something new and innovative. But this time we hope it will make a lasting impression and, therefore, that it will be the first book in a series of future DAPMARC Proceedings. DAPMARC was born out of a Research Initiative that the Organization Dansk Projektledelse started years ago. The two of us (Per Svejvig and Jan Pries-Heje) have been meeting regularly within this initiative for the last 4-5 years. About a year ago we had a discussion about how we could better integrate theory with practice one more time. When we say one more time it is because we succeeded in publishing a state-of-the-art book with Danish research on Project Management in 2013 (Pries-Heje, Jan (ed.) (2013). Project Management Multiplicity: Current Trends. Samfundslitteratur). But now the idea was to integrate a research conference within the Project Symposium that Dansk Projektledelse has been organizing since We thought that was an excellent idea and grasped the opportunity to do so and here is the book. Following this line of thought we want to thank Morten Fangel and Jesper Garde Schreiner, both from Dansk Projektledelse, for their cooperation. Without their backing and willingness to think in a new way about the Project Symposium this book and DAPMARC would never had happened. The process bringing us to this book started in October We produced a call for papers and initiated an EasyChair submission and reviewing page. In the call we identified the theme of the Conference to be Theory Meets Practice in Projects, and we asked for submissions within the following areas of project management: Situational project management Innovation, creativity and entrepreneurship Strategic management of portfolios, programs and projects Project management office
7 6 Foreword DAPMARC 2015 People, leadership and professionalism Stakeholder management Agile project management Leadership, governance and decision making Collaboration, trust and relationships Project-based organizations and networks We received 12 submissions. All 12 were sent out to at least two reviewers from the program committee, consisting of: Anita Mac, Associate Professor, Roskilde University Charles Møller, Professor, Aalborg University Eva Riis, Researcher, Southern Danish University Jacob Nørbjerg, Associate Professor, Aalborg University and Copenhagen Business School Anita Friis Sommer, Researcher, Aalborg University Kasper Edwards, Senior Researcher, Danish Technical University Constance Elisabeth Kampf, Associate Professor, Aarhus University Peter Axel Nielsen, Professor, Aalborg University Ivan Aaen, Associate professor, Aalborg University Pernille Kræmmergaard, Professor, Aalborg University and The IT University of Copenhagen Lene Pries-Heje, Associate Professor, The IT University of Copenhagen Sara Grex, Assistant Professor, Danish Technical University Jesper Schlamovitz, Assistant Professor, Roskilde University We want to take this opportunity to thank everyone in the Program Committee for their excellent and insightful reviews. We are certain that all authors benefitted significantly from the high quality of the reviews. While the reviews were carried out we contacted potential publishers. We wanted to publish with a publisher listed in the Danish Bibliometric Research Indicator we had said that in the call for papers and were certain that it was a strong motivator for the researchers submitting papers. Roskilde Universitetsforlag seemed very appropriate as Roskilde Universitet is one of the Universities in Denmark that are most engaged in Project Management Research. We want to
8 Foreword DAPMARC take this opportunity to thank Annette Kjølby who represented the publisher for her excellent work and responsiveness. In the beginning of February we The Editors met to look at all the reviews. In a few cases we decided that we needed to do one more review ourselves. But in all cases we wrote an Editorial Report with our decision on whether to accept or reject the paper. The accept or reject decision was hard to make. We had nine papers of sufficient quality with at least one reviewer positive about the paper at this point. Nevertheless we decided to accept eight papers for this book, based on what fitted the theme Theory Meets Practice in Projects best. Authors were then given three weeks to cope with all the review and editorial comments and on the last day of February we gathered all the papers, added this foreword, and thereby had this book. As Editors of the book, and as General Chairs and Program Chairs for DAP- MARC, we are proud to present a book of such high quality. We hope you our reader will enjoy the content now and for many future years. Jan Pries-Heje and Per Svejvig
9 8
10 CONTENTS Foreword DAPMARC Are Heroes All We Need? The New Role of the IT Project Manager 11 Gitte Tjørnehøj, Andreas Saxkjær Jespersen and Theis von Moos 2. Fast or Smart? How the Use of Scrum Can Influence the Temporal Environment in a Project 39 Vibeke Kristine Scheller, Jan Pries-Heje and Helge Søndergård Hvid 3. Hidden Goals in Projects: A Qualitative Exploratory Study of Their Occurrence and Causes 61 Pekka Buttler 4. Frontload in Complex Project Program Management to Aim for Lifetime Sustainability of Offshore Windmill Parks 73 Tove Brink 5. Metaphors in Projects An Overlooked X-Factor 87 Per Svejvig 6. Bridging Gaps between IT and Business: An Empirical Investigation of IT Project Portfolio Management Using Process Mining and P3M3 Maturity Model 101 Nazli Shahim and Charles Møller 7. Governance of Projects and Value Generation in Project-oriented Organizations 117 Eva Riis 8. Theory Meets Practice: Practical Implications of Process Theory in Project Management 139 Jesper Schlamovitz
11
12 PROJECT MANAGEMENT THEORY MEETS PRACTICE ARE HEROES ALL WE NEED? THE NEW ROLE OF THE IT PROJECT MANAGER ARE HEROES ALL WE NEED? THE NEW ROLE OF THE IT PROJECT MANAGER Gitte Tjørnehøj, Aalborg University, Denmark, Andreas Saxkjær Jespersen, Bankdata, Denmark, Theis von Moos, Aalborg University, Denmark, ABSTRACT More and more software firms adopt agile methods into their practice to become more flexible and increase their speed to market. To get the best from both worlds they often choose to balance agility with traditional approaches. This complicates the job for the project managers especially. This paper identifies motives, opportunities and challenges for organizations to balance and categorizes types of balancing as the basis for investigating the new project manager role of balanced systems development. It builds a theoretically based framework of the role of the project manager when balancing and renders it probable through two distinct different case studies one of a born-agile organization introducing traditional practices and the other of a traditional organization introducing agility. The paper describes theoretically and empirically based complexity and overload of the new project management role. It identifies a new beneficial shallow type of balancing and suggests solutions in line with this. An alternative solution is to form self-organizing project management teams to decrease the load on the individual and increase the pool of skills and reflections in the management of projects. Keywords: Balancing, Agility, Traditional Systems Development, Project Managing, IT Project Manager, Boundary Spanning, Ambidexterity, Overload, Stress, Shallow Balancing, Self-Organizing Project Management Team INTRODUCTION Systems development practice is under transformation to meet new demands caused by the increasing demand for information systems in business, government and society. Rapid growth in use areas, new technologies and challenges of
13 12 Are Heroes All We Need? The New Role of the IT Project Manager technical integration, customer knowledge and expectations has created a rapidly changing and very demanding market for software firms. Pampered customers want high quality, inexpensive, useful and integrated software for everything and they want it now. This, together with an expanding global software market, puts the firms under pressure to increase their adaptability, flexibility and speed to market (Baskerville et al. 2011). Many newly formed firms are created to be good at exactly that, while established firms often struggle to match the market. Traditionally, the challenges of software development have been complexity and quality, which has been handled through the standardization of comprehensive processes prescribing the appropriate activities, tools and artifacts needed in these professional software practices. The Rational Unified Process (Kruchten 2004) and CMMI (Humphrey 1989; McFeeley 1996; The CMMI product team 2001) are high-profile examples of these approaches that are commonly called traditional, disciplined or plan-driven, because of their emphasis on planning and control. Most professional software firms have organized their systems development practice in accordance with these principles, with more or less successful results. That was until the recent wave of agility. The traditional principles go well with a centralized, top down managed and rather bureaucratic company culture that can be argued to fit better in the late industrial age (Rose et al. 2008). Thus many firms fight to overcome the new challenges of systems development by new means, as the old way has proven insufficient. Agile methods promise flexible, efficient and effective systems development (Beck et al. 2001; Beck and Boehm 2003), which seem to be exactly what the software firms need. But still the virtues of traditional software development appear to be somewhat beneficial. Recent research concludes that most firms strive to reconcile the traditional approaches with agility into new, more suitable, practices (Magdaleno et al. 2012). Apparently it is a post-agility era, where balancing agility and the traditional approaches is the new trend of systems development, even for the born-agile firms (Baskerville et al. 2011). Introducing agile methods in traditional practices, or vice versa, is a difficult mission (Baskerville et al. 2011; Boehm and Turner 2003a). The complexities at all levels, and in all relations, increase as two disparate worlds of assumptions, methods, practices and tools needs to be handled, integrated and understood by all involved. This may cause difficulties and Baskerville et al. (2011) emphasize that boundary spanning by key persons is important to integrate the distinct social worlds of balancing. This research finds that the key persons in the boundary spanning could easily
14 PROJECT MANAGEMENT THEORY MEETS PRACTICE 13 be the IT project managers and that they play a significant role in eroding the experienced boundaries. We investigate how the increasingly challenging and complex situation affects the IT project managers. As most software development has the nature of uncertainty it is organized as projects, giving the project manager a key position in the production of the software managing the people, the processes and the products. The question is what role the project manager plays in software firms when balancing agile and traditional software development? Most published research on balancing focuses on the aspect of processes, for example, investigating attempts to combine practices from CMMI/ISO, XP and Scrum. Our research sheds light on the challenges and opportunities at the organizational and project level as suggested by Magdaleno et al. (2012), by developing a theoretical framework for understanding the (new) role of the IT project manager. The framework is developed from a literature study and rendered probable through two small but distinct different case studies one traditional software firm striving to adopt agility and a born-agile firm adopting certain traditional practices to consolidate their business. The paper is structured as follows: First the research approach is described, then a section on balancing agile and traditional systems development provides an overview of the existing knowledge on why and how to balance, before the framework focusing on how balancing influences the role of the project manager is presented and argued. The case analysis presents the results from the two case studies, and the cross analysis discuss what parts of the framework are rendered probable by the cases and zooms in on the role of the project manager for comparison. The discussion elicits implications for practice and the conclusion sums up, answers the research question and suggests further research. RESEARCH APPROACH This research constructs a theoretically based framework for the role of the IT project manager in organizations balancing agility and traditional systems development. The framework is rendered probable through two minor case studies. As balancing of agility and traditional systems development is a rather new phenomenon in the complex context of the software industry, it is feasible to investigate through case studies (Yin 2009). Through a literature study the existing knowledge of balancing were mapped (Yin 2009, p. 14), and served as the analytical framework for the case study. The cases were chosen to be distinctly different
15 (1) Accommodated communication Management (steering committee etc.) (7) Feedback E.g. changed plans Technological environments (11) Expectations management Artefacts Controls the content Accommodated communication Coach Product /facilitator owner /motivator Coaching incl. on Architect technical aspects Plan work and delegates Responsible for the rather detailed (14) architectural quality (13) Controls the Gate keeper of the solution content Direct control and Feedback management (4) (12) (5) Traditional developmet Team(s) (6) (8) Overall responsible for the project and for aligning plans, people and long-term goals The Project manager (9) Accommodated Accommodated communication communication (5) Artefacts Balancing the approaches through risk assesment (15) Product (2) Stakeholders cutomers, users etc. (7) Feedback E.g. changed requirements Expectations management (10) The agile development Team(s) Agile context: The scrum master focus on today and to morrow, while the team is self-organizing 14 Are Heroes All We Need? The New Role of the IT Project Manager as the born-agile firm were rapidly growing, feeling the need for more structure and discipline in certain parts of their processes, and the traditional middle sized software firm in the financial sector were starting to adopt agile methods needing more flexibility. Exploratory pilot study? Literature studies Construct framework Balancing from agility Data collection & analysis Data collection & analysis Interpreting Balancing from traditional Interpreting Result Result Cross case analysis Similarities and differences across contexts DEVELOPMENT LAYER STRATEGIC LAYER Monitoring and evaluating technology to integrate Figure 1.1. The research process has been iterative in both the construction of the framework based on the literature review and in the process of rendering the framework probable through the case studies. First, an explorative pilot study (two interviews) on challenges of adopting agility helped focus our attention on the project manager as the key person. Second a literature study was designed focusing on both balancing and on the project managers role in balancing. This literature study followed a structured approach recommended in Webster and Watson (2002). The literature was analyzed through three distinct questions: 1) why balancing? 2) How can balancing be done? and 3) how does balancing influence the role of the project manager? The results were displayed in concept matrixes and the finds, from question 3 especially, laid the ground for developing the theoretical framework by attempting to pin bits and pieces from the literature together to create a meaningful whole describing the new role of the project manager. The two case studies were designed as parallels in terms of interview guide, data collection and analysis. For practical reasons we had four interviews in the traditional organization across the organizational levels and only two in the born-agile organization, covering the same span of organizational levels. The parallel design allows for cross case analysis (Yin 2009) investigating how balancing is played out in different contexts and the effects on the role of the project manager.
16 PROJECT MANAGEMENT THEORY MEETS PRACTICE 15 The constructed framework served as the interview guide in the open ended interviews, where the interviewees discussed and evaluated the match of the framework to their perceptions of practice. Notes were taken, or drawn onto the model, in collaboration with the interviewee. The interviews were sound recorded, transcribed and tagged by two researchers, individually, and the results compared and negotiated. The data, organized this way, was analyzed and interpreted with the purpose of rendering the framework probable by comparison to the studied practices. Based on this the framework was further developed and any new aspect discovered was added. Even though the data collection and analysis of the two cases were undertaken in parallel the case of balancing from traditional practice turned out to be far more complex in terms of organization, challenges and diversity than the agile case. Thus the traditional case is reported in more detail. BALANCING AGILE AND TRADITIONAL SYSTEMS DEVELOPMENT APPROACHES Despite early discourses about agility and traditional systems development to be irreconcilable paradigms (Beck and Boehm 2003), research now concludes that it is beneficial to balance agile and traditional approaches (Magdaleno et al. 2012). The concept of balancing suggests that both agile and traditional approaches have their home grounds of organizational conditions under which the approaches are most likely to succeed (Boehm and Turner 2003d). Systems development projects should be evaluated according to the home grounds and balanced approaches should be tailored to match the project (Boehm and Turner 2003c; Port and Bui 2009). Since systems development projects are rarely positioned entirely on either home ground (Galal-Edeen et al. 2007), combining methods (balancing) are most often recommended. Why balance? Motives, opportunities and challenges Across all the contributions on balancing, motives, opportunities and challenges are discussed widely. The motive most often mentioned is that neither agile nor traditional approaches are complete solutions (Boehm and Turner 2003b; Boehm and Turner 2003d; Boehm and Turner 2005; Boehm 2002; Galal-Edeen et al. 2007; Jakobsen and Johnson 2008; Lukasiewicz and Miler 2012; Lycett et al. 2003; Magdaleno et al. 2012; Marcal et al. 2007; Nawrocki et al. 2006; Port and Bui
17 16 Are Heroes All We Need? The New Role of the IT Project Manager 2009; Vinekar et al. 2006). Balancing is a kind of general solution allowing for pragmatic handling of a wide range of challenges, since both agile and traditional methods have their separate strengths. There is a need to maintain dual structures that accommodate both approaches (Vinekar et al. 2006) since a changing world requires both agility and discipline (Nawrocki et al. 2006). Opportunities are that balancing can drive process optimization, increase flexibility and reduce cost and time to market by pragmatic utilization of the optimizing aspect of the traditional approaches combined with the flexibility and low overhead cost of agility (Boehm and Turner 2003d; Galal-Edeen et al. 2007; Lepmets and Nael 2010; Lukasiewicz and Miler 2012; Port and Bui 2009; Vinekar et al. 2006). Superfluous processes can be diminished (Little 2005) and thus the processes can be optimized (Marcal et al. 2007). Project failures can decrease (Venugopal 2005) and quality can improve (Magdaleno et al. 2012). The close customer contact of agility (Baskerville et al. 2011) and the team communication (Pikkarainen 2009) is especially pinpointed as beneficial, while the traditional virtue of documentation is emphasized to increase visibility, scalability and reliability of the solution (Beck and Boehm 2003). Boehm and Turner (2005) formulate the main challenge of balancing as the need to avoid development process conflicts that can ruin the agility and undermine the optimization already achieved by traditional practice over the years. It is crucial to exploit the strengths of the approaches and minimize the weaknesses (Boehm and Turner 2003d; Marcal et al. 2007). The key to successful balancing is handling people, values, communication and expectations (Boehm and Turner 2003b). Coordination and communication are thus core challenges (Baskerville et al. 2011; Boehm and Turner 2005; Galal-Edeen et al. 2007; Lycett et al. 2003; Magdaleno et al. 2012). Organizational culture is important and can be a barrier (Galal-Edeen et al. 2007; Karlström and Runeson 2005; Lukasiewicz and Miler 2012; Magdaleno et al. 2012; Vinekar et al. 2006). Handling the diverging culture and contradictory work processes of the approaches can be a severe management challenge (Pikkarainen 2009). Engaging everybody in the change processes is crucial (Boehm and Turner 2005; Vinekar et al. 2006), but hard because the dissimilarity of the approaches often require radical changes by individuals (Baskerville et al. 2011; Vinekar et al. 2006).
18 PROJECT MANAGEMENT THEORY MEETS PRACTICE 17 How can balancing be done? Types of balancing The literature discusses three different types of balancing, depending on the organizational level in focus. Literature on project based balancing focuses on tailoring approaches at project level, using general concepts of plan-driven and agility without being methodological specific. The main contributions are the above mentioned texts of home grounds. Alternatively, balancing by the principle of ambidexterity (Raisch et al. 2009) at project level is also suggested, subscribing parts of the development work to separate organizational units for agility and stability respectively (Galal-Edeen et al. 2007; Vinekar et al. 2006). Contributions on methodological balancing target balancing, by constructing hybrid light weight methods by combining specific practices from specific methods. An example is XPrince (Nawrocki et al. 2006) that combines XP (Beck 2003), Prince2 (Bentley 2009) and RUP (Kruchten 2004). The balance should be reached by striving towards minimal methodological structure that are not being laissez-faire, i.e. integrating only the necessary elements of the involved methods (Jakobsen and Johnson 2008; Little 2005; Lycett et al. 2003; Marcal et al. 2007; Nawrocki et al. 2006). The assumption of contributions on organizational balancing is that successful balancing is dependent on the capability of the organization when handling the ambiguity between agility and traditional approaches. Different approaches to achieve balancing (Little 2005; Lycett et al. 2003; Venugopal 2005) and theories providing understanding of balancing (Baskerville et al. 2011; Karlström and Runeson 2005) are presented with the effects on the organization in focus. It is highlighted that when organizations embark on balancing, they need to be aware that it is an organizational change process they need to master (Baskerville et al. 2011; Little 2005; Lycett et al. 2003; Venugopal 2005). Baskerville et al. (2011) concludes from a longitudinal study of balancing that combining agile and traditional methods will be necessary in the post-agility era. A reintroduction of the traditional project manager role in agility is required because of the limited scope of Scrum (Schwaber and Beedle 2001). Karlström and Runeson (2005) focus on the project manager role in both agile and traditional methods, and they map the pros and cons of balancing in a stage-gate model. They suggest combination of the agile aspects for optimizing daily planning, and the traditional aspects for securing long term overview in project management.
19 18 Are Heroes All We Need? The New Role of the IT Project Manager THE INFLUENCE OF BALANCING ON THE ROLE OF THE IT PROJECT MANAGER CONSTRUCTING THE FRAMEWORK The framework was constructed based on knowledge of the role of the project manager when balancing, found in the literature review, and on basic knowledge about agile and traditional approaches. None of the studied literature focused explicitly on project management, but many mentioned aspects of the role or aspects that could influence the role. When balancing, a project manager basically needs to master both agile and traditional project management, but balancing in itself seems to add more tasks and demand more from the project manager. This framework elaborates on all these intertwined aspects as a whole and serves as a proposition of how balancing will influence the role of the project manager. The framework thus expresses the existing theoretical knowledge of this topic. Based on the project managers traditional position as the boundary spanner of the project, the framework is divided into a strategic and development layer with the project manager linking the two as a vital all-rounder (1). The project manager is expected to handle the dualism of keeping the full overview of the project, and tracking plans and milestones, in the strategic layer while, in the development layer, also coaching and protecting the development team from outside disturbances. The last is especially evident in agile approaches. Baskerville et al. (2011) argues that, when balancing, the project manager needs to fill the role as boundary spanner between the day-to-day systems development in the team and the customers and management that need to know about progress and quality of the product. Important actors in the strategic layer are the management (2) and stakeholders (3), while in the development layer the project manager potentially deals with both traditional (4) and agile development teams (5) (Galal-Edeen et al. 2007). In the strategic layer the project manager should develop a widely agreed upon vision, establish the frames for the project and develop artifacts, such as plans (6), that can be utilized to accommodate the communication to the actors of the layer management and other outside stakeholders (Boehm and Turner 2003d; Nawrocki et al. 2006). The most important task in the strategic layer is thus stakeholder communication and expectations management (7) and the project manager generally has the overall responsibility for aligning plans, people and long term goals for the project (8).
20 PROJECT MANAGEMENT THEORY MEETS PRACTICE 19 At the same time the project manager should be capable of playing a range of roles such as facilitator, coach and motivator (9) in the actual work of the project and in managing the development work (Baskerville et al. 2011; Boehm and Turner 2005; Nawrocki et al. 2006). The architect (10) is responsible for the technical aspect of the solution. The literature disagrees on whether this responsibility should be integrated with the project manager role (Jakobsen and Johnson 2008) or not (Nawrocki et al. 2006). Thus the architect role is depicted separately in the framework. The responsibility for watching and evaluating new technologies to integrate in the solution is also mentioned as the responsibility of the project manager (11) (Boehm and Turner 2003d). This responsibility does not really fit in the layers, but demand that the project manager has some of his focus outside the project on the technical environments. There may be more of these distracting responsibilities not fitting in depending on the situation. STRATEGIC LAYER DEVELOPMENT LAYER (1) Accommodated communication Management (steering committee etc.) (7) Feedback E.g. changed plans Technological environments (11) Expectations management Plan work and delegates rather detailed (13) Direct control and management Traditional development Team(s) (2) (3) (6) Monitoring and evaluating technology to integrate Accommodated communication Artifacts Controls the content (8) Overall responsible for the project and for aligning plans, people and long-term goals The Project manager (9) Coach /facilitator /motivator Controls the content Feedback Accommodated communication Accommodated communication Artifacts Balancing the approaches through risk assessment Product Product owner Stakeholders customers, users etc. (7) Feedback E.g. changed requirements Coaching incl. on technical aspects (14) Gate keeper Expectations management Architect Responsible for the architectural quality of the solution (4) (12) (5) (15) (10) The agile development Team(s) Agile context: The scrum master focus on today and tomorrow, while the team is self-organizing Figure 1.2. The role of the project manager in organizations balancing agile and traditional approaches. The numbers (x) refer to numbers in the text describing the framework.
Software 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 informationwww.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Created by Stephen Barkar - www.stephenbarkar.se
1 www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Purpose with the material 2 This material describes the basics of Agile and Lean and the similarities and differences between
More informationFive Core Principles of Successful Business Architecture. STA Group, LLC Revised: May 2013
Five Core Principles of Successful Business Architecture STA Group, LLC Revised: May 2013 Executive Summary This whitepaper will provide readers with important principles and insights on business architecture
More informationBecoming Agile: a getting started guide for Agile project management in Marketing, Customer Service, HR and other business teams.
Becoming Agile: a getting started guide for Agile project management in Marketing, Customer Service, HR and other business teams. Agile for Business www.agilefluent.com Summary The success of Agile project
More informationAGILE SOFTWARE DEVELOPMENT A TECHNIQUE
AGILE SOFTWARE DEVELOPMENT A TECHNIQUE Saurav Tiwari 1,Aasheesh Goel 2,Rajeev Sharma 3 1,2 Research Scholar,MCADept.,SRM University,NCRCampus,Modinagar 3 Asst. Prof.,MCADept.,SRM University,NCR Campus
More informationIncreasing Development Knowledge with EPFC
The Eclipse Process Framework Composer Increasing Development Knowledge with EPFC Are all your developers on the same page? Are they all using the best practices and the same best practices for agile,
More informationEnvisioning a Future for Public Health Knowledge Management
Envisioning a Future for Public Health Knowledge Management By Cadence Group Public health today faces challenges and opportunities of a degree that it has never seen before. Never before have methods
More informationAbstract. Keywords: Program map, project management, knowledge transition, resource disposition
Journal of Economic Development, Management, IT, Finance and Marketing, 6(1), 1-22, March 1 How to Prepare a Program Roadmap Kevin Byrne, Robert Keys, Cynthia Schaffer, Andrew N. Solic Drexel University,
More informationBecoming Agile: a getting started guide for Agile management in Marketing and their partners in IT, Sales, Customer Service and other business teams.
Becoming Agile: a getting started guide for Agile management in Marketing and their partners in IT, Sales, Customer Service and other business teams. Agile for Business www.agilefluent.com Summary The
More informationAs the use of agile approaches
What Does a Business Analyst Do on an Agile Project? By Kent J. McDonald Senior Instructor, B2T Training As the use of agile approaches increases, business analysts struggle to determine how their role
More informationBuilding Software in an Agile Manner
Building Software in an Agile Manner Abstract The technology industry continues to evolve with new products and category innovations defining and then redefining this sector's shifting landscape. Over
More informationAgile-Fall Process Flow Model A Right Candidate for Implementation in Software Development and Testing Processes for Software Organizations
www.ijcsi.org 457 Agile-Fall Process Flow Model A Right Candidate for Implementation in Software Development and Testing Processes for Software Organizations Prakash.V SenthilAnand.N Bhavani.R Assistant
More informationAgile So)ware Development
Software Engineering Agile So)ware Development 1 Rapid software development Rapid development and delivery is now often the most important requirement for software systems Businesses operate in a fast
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationFamily Evaluation Framework overview & introduction
A Family Evaluation Framework overview & introduction P B Frank van der Linden O Partner: Philips Medical Systems Veenpluis 4-6 5684 PC Best, the Netherlands Date: 29 August, 2005 Number: PH-0503-01 Version:
More informationCREATING A LEAN BUSINESS SYSTEM
CREATING A LEAN BUSINESS SYSTEM This white paper provides an overview of The Lean Business Model how it was developed and how it can be used by enterprises that have decided to embark on a journey to create
More informationAgile Engineering Introduction of a new Management Concept
Journal of Applied Leadership and Management 4, 39-47 39 Agile Engineering Introduction of a new Management Concept Philipp Hecker (philipp.hecker_ch@bluewin.ch) Artur Kolb (arthur.kolb@hs-kempten.de)
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 informationChanging Roles and Responsibilities from Traditional project management to Agile project management
Changing Roles and Responsibilities from Traditional project management to Agile project management Vishvadeep Tripathi School of computer science and IT Devi Ahilya University Indore, India vishvadeep@gmail.com
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 informationBenefits Realization from IS & IT, and Change Management of roles and the working practices of individuals and teams.
: Delivering Value from IS & IT Investments John Ward and Elizabeth Daniel John Wiley & Son Ltd ISBN: 9780470094631, 399 pages Theme of the Book This book explores a process and practical tools and frameworks
More informationIntroducing Reference Models in ERP Development
Introducing Reference Models in ERP Development Signe Ellegård Borch IT University of Copenhagen elleborch@itu.dk Introduction Business process reference modelling is not a new topic in the ERP software
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationAgile Development Overview
Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others
More informationAgile for Project and Programme Managers
Agile for Project and Programme Managers Author Melanie Franklin Director Agile Change Management Limited Introduction I am involved in a mixture of assignments for different organisations across Europe
More informationAgile Training Portfolio
Agile Training Portfolio Why agile? The question can also be: Why learn fast? Why adapt to new experiences and learnings quickly and easily? Well, the Dodo was not very agile and we all know how that ended.
More informationPEOPLE INVOLVEMENT AND THEIR COMPETENCE IN QUALITY MANAGEMENT SYSTEMS * Jarmila ŠALGOVIČOVÁ, Matej BÍLÝ
PEOPLE INVOLVEMENT AND THEIR COMPETENCE IN QUALITY MANAGEMENT SYSTEMS * Jarmila ŠALGOVIČOVÁ, Matej BÍLÝ Authors: Workplace: Assoc. Prof. Jarmila Šalgovičová, PhD., Prof. Matej Bílý, DrSC.* Institute of
More informationComputing & Communications Services
2010 Computing & Communications Services 2010 / 10 / 04 Final Kent Percival, M.Sc., P.Eng. Defining the Value of the Business Analyst In achieving its vision, key CCS partnerships involve working directly
More informationAGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson 23.11.2005 Jyväskylä
AGILE SOFTWARE DEVELOPMENT: INTRODUCTION, CURRENT STATUS & FUTURE Pekka Abrahamsson 23.11.2005 Jyväskylä Fact corner: SME of 250 developers Mobile & desktop sw Products sold globally EXAMPLE OF AN INNOVATIVE
More informationQuality Assurance in an Agile Environment
Quality Assurance in an Agile Environment 1 Discussion Topic The Agile Movement Transition of QA practice and methods to Agile from Traditional Scrum and QA Recap Open Discussion www.emids.com 2 What is
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 informationBehaviourally Based Questions
Behaviourally Based Questions Index 1 HOW TO WRITE BEHAVIOURALLY BASED QUESTIONS Page 2 2 SAMPLE BEHAVIOURAL QUESTIONS Page 3 3 SAMPLE BEHAVIOURALLY BASED QUESTIONS FROM RIGHT JOB, RIGHT PERSON! CAPABILITY
More informationArchitecting enterprise BPM systems for optimal agility
Architecting enterprise BPM systems for optimal agility Dr Alexander Samarin www.samarin.biz About me An enterprise solutions architect From a programmer to a systems architect Experience in scientific,
More informationBridging the Gap: Traditional to Agile Project Management. I. S. Parente 1. Susan Parente, PMP, PMI ACP, CISSP, PMI RMP, ITIL, MSEM;
Bridging the Gap: Traditional to Agile Project Management ABSTRACT I. S. Parente 1 1 Susan Parente, PMP, PMI ACP, CISSP, PMI RMP, ITIL, MSEM; S3 Technologies, LLC, Principal Consultant; parente@s3 tec.com
More informationA Framework for Software Product Line Engineering
Günter Böckle Klaus Pohl Frank van der Linden 2 A Framework for Software Product Line Engineering In this chapter you will learn: o The principles of software product line subsumed by our software product
More information7 Conclusions and suggestions for further research
7 Conclusions and suggestions for further research This research has devised an approach to analyzing system-level coordination from the point of view of product architecture. The analysis was conducted
More informationSoftware processes that are:
Agile Processes Software processes that are: Incremental (small software releases with rapid cycles) Cooperative (customer and developer working together with close communication) Straightforward (method
More informationA Comparison of SOA Methodologies Analysis & Design Phases
202 A Comparison of SOA Methodologies Analysis & Design Phases Sandra SVANIDZAITĖ Institute of Mathematics and Informatics, Vilnius University Abstract. Service oriented computing is a new software engineering
More informationAgile Software Development Methodologies and Its Quality Assurance
Agile Software Development Methodologies and Its Quality Assurance Aslin Jenila.P.S Assistant Professor, Hindustan University, Chennai Abstract: Agility, with regard to software development, can be expressed
More informationProject Management Office
Whitepaper Project Management Office sqs.com PMO as a strategic success factor for project-based organisations Abstract Project-management-based organisations with either large or numerous projects can
More informationTaking the first step to agile digital services
Taking the first step to agile digital services Digital Delivered. Now for Tomorrow. 0207 602 6000 mbailey@caci.co.uk @CACI_Cloud 2 1. Background & Summary The Government s Digital by Default agenda has
More informationComparing Plan-Driven and Agile Project Approaches
Comparing Plan-Driven and Agile Project Approaches A Personal Perspective Presented by: Craig D. Wilson Matincor, Inc. Copyright 2006-2010 2010 Outline Introduction to System Development Methodology Contrasting
More informationTable of contents. Performance testing in Agile environments. Deliver quality software in less time. Business white paper
Performance testing in Agile environments Deliver quality software in less time Business white paper Table of contents Executive summary... 2 Why Agile? And, why now?... 2 Incorporating performance testing
More informationSoftware Development with Agile Methods
Case Study Software Development with Agile Methods Introduction: Web application development is a much studied, heavily practiced activity. That is, capturing and validating user requirements, estimating
More informationAn Ideal Process Model for Agile Methods
An Ideal Process Model for Agile Methods Marcello Visconti 1 and Curtis R. Cook 2 1 Departamento de Informática, Universidad Técnica Federico Santa María, Valparaíso, CHILE visconti@inf.utfsm.cl 2 Computer
More informationAgile Systems Engineering: What is it and What Have We Learned?
Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman Suzette.Johnson@ngc.com Getting To Know You! Dr. Suzette Johnson Northrop
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 informationSoft Skills Requirements in Software Architecture s Job: An Exploratory Study
Soft Skills Requirements in Software Architecture s Job: An Exploratory Study 1 Faheem Ahmed, 1 Piers Campbell, 1 Azam Beg, 2 Luiz Fernando Capretz 1 Faculty of Information Technology, United Arab Emirates
More informationCover Page. The handle http://hdl.handle.net/1887/33081 holds various files of this Leiden University dissertation.
Cover Page The handle http://hdl.handle.net/1887/33081 holds various files of this Leiden University dissertation. Author: Stettina, Christoph Johann Title: Governance of innovation project management
More informationDeveloping Teacher Leadership and its Impact in Schools M. Snoek
Developing Teacher Leadership and its Impact in Schools M. Snoek SUMMARY DEVELOPING TEACHER LEADERSHIP AND ITS IMPACT IN SCHOOLS Introduction Successful school improvement is dependent on schools capacities
More informationEXECUTIVE BEHAVIORAL INTERVIEW GUIDE
EXECUTIVE BEHAVIORAL INTERVIEW GUIDE INTERVIEW GUIDE INSTRUCTIONS: This Interview Guide is intended to help hiring executives conduct behavioral interviews for executive classifications covered by the
More informationAgile Governance. Charlie Rudd SollutionsIQ. Copyright 2011 SolutionsIQ. All rights reserved.
Agile Governance Charlie Rudd SollutionsIQ Speaker Introduction: Charlie Rudd CEO of SolutionsIQ, an Agile company that provides Agile services including consulting, training, software development and
More informationBasic Management Principles. Author: Jack E. Fincham, PhD, RPh Dean & Professor University of Kansas School of Pharmacy
Basic Management Principles Author: Jack E. Fincham, PhD, RPh Dean & Professor University of Kansas School of Pharmacy Learning Objectives Understand basic management principles applying to individuals,
More informationLecture Slides for Managing and Leading Software Projects. Chapter 1: Introduction
Lecture Slides for Managing and Leading Software Projects Chapter 1: Introduction developed by Richard E. (Dick) Fairley, Ph.D. to accompany the text Managing and Leading Software Projects published by
More informationBusiness Modeling with UML
Business Modeling with UML Hans-Erik Eriksson and Magnus Penker, Open Training Hans-Erik In order to keep up and be competitive, all companies Ericsson is and enterprises must assess the quality of their
More informationApplying Agile Methods in Rapidly Changing Environments
Applying Agile Methods in Changing Environments 7/23/2002 1 Applying Agile Methods in Rapidly Changing Environments Peter Kutschera IBM Unternehmensberatung GmbH Am Fichtenberg 1, D-71803 Herrenberg Steffen
More informationThe Logical Framework Approach An Introduction 1
The Logical Framework Approach An Introduction 1 1. What is the Logical Framework Approach? 1.1. The background The Logical Framework Approach (LFA) was developed in the late 1960 s to assist the US Agency
More informationProcess Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
More informationThe Changing Role of Software Tester
The Changing Role of Software Tester Anna Royzman ari16a@gmail.com Abstract In 2008 my company reorganized into product units and adopted Agile process methodology. As a result, my QA manager position
More informationThe Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July 2013. Developed and sustained by Ken Schwaber and Jeff Sutherland
The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide... 3 Definition of
More informationPresented By: Leah R. Smith, PMP. Ju ly, 2 011
Presented By: Leah R. Smith, PMP Ju ly, 2 011 Business Intelligence is commonly defined as "the process of analyzing large amounts of corporate data, usually stored in large scale databases (such as a
More informationStrategic View on Various Sub-paradigms of Agile Methodology and Sig Sigma Approach
International Journal of Information and Computation Technology. ISSN 0974-2239 Volume 3, Number 3 (2013), pp. 153-162 International Research Publications House http://www. irphouse.com /ijict.htm Strategic
More informationLasting commercial success with Agile Evolution
Turning visions into business December 2011 Lasting commercial success with Agile Evolution Malte Foegen, David Croome, Timo Foegen Scrum techniques are spreading increasingly. In many cases, they lead
More informationNo one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Scrum
No one has to change. Survival is optional. - W. Edwards Deming - Continue your Beyond Budgeting Journey with help from Agile, Lean and Helge Eikeland, Statoil, October 2010 Today s challenge is complexity
More informationAGILE METHODOLOGY IN SOFTWARE DEVELOPMENT
AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT Shivangi Shandilya, Surekha Sangwan, Ritu Yadav Dept. of Computer Science Engineering Dronacharya College Of Engineering, Gurgaon Abstract- Looking at the software
More informationA Roadmap to Agile Development: A Strategy to Increase Adoption Success
A Roadmap to Agile Development: A Strategy to Increase Adoption Success Executive Summary Organizations that try to adopt Agile too quickly are often discouraged with less than stellar results, and they
More informationWeb Application Development Process
Web Engineering Web Application Development Process Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements
More informationAttribute 1: COMMUNICATION
The positive are intended for use as a guide only and are not exhaustive. Not ALL will be applicable to ALL roles within a grade and in some cases may be appropriate to a Attribute 1: COMMUNICATION Level
More informationFive best practices for deploying a successful service-oriented architecture
IBM Global Services April 2008 Five best practices for deploying a successful service-oriented architecture Leveraging lessons learned from the IBM Academy of Technology Executive Summary Today s innovative
More informationIntegrating Scrum with the Process Framework at Yahoo! Europe
Integrating Scrum with the Process Framework at Yahoo! Europe Karl Scotland Yahoo! Europe kjscotland@yahoo.co.uk Alexandre Boutin Yahoo! International alexandre.boutin@yahoo-inc.com Abstract Large enterprise
More informationHow To Change A Business Model
SOA governance and organizational change strategy White paper November 2007 Enabling SOA through organizational change Sandy Poi, Global SOA Offerings Governance lead, associate partner, Financial Services
More informationChapter 12. The Product Coordination Team
Chapter 12. The Product Coordination Team In theory, theory and practice are the same. In practice, they are different. Attributed to many. In This Chapter This chapter describes the challenge of teams
More information3 rd GENERATION KNOWLEDGE MANAGEMENT and Beyond!
KNOWLEDGE MANAGEMENT TALKS: 3 rd GENERATION KNOWLEDGE MANAGEMENT and Beyond! Even given its short life span, Knowledge Management has clearly evolved through three distinct eras, and is already entering
More informationREGULATIONS AND CURRICULUM FOR THE MASTER S PROGRAMME IN INFORMATION ARCHITECTURE FACULTY OF HUMANITIES AALBORG UNIVERSITY
REGULATIONS AND CURRICULUM FOR THE MASTER S PROGRAMME IN INFORMATION ARCHITECTURE FACULTY OF HUMANITIES AALBORG UNIVERSITY SEPTEMBER 2015 Indhold PART 1... 4 PRELIMINARY REGULATIONS... 4 Section 1 Legal
More informationAgile Master Data Management A Better Approach than Trial and Error
Agile Master Data Management A Better Approach than Trial and Error A whitepaper by First San Francisco Partners First San Francisco Partners Whitepaper Executive Summary Market leading corporations are
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationPORTFOLIO MANAGEMENT: LESSONS LEARNED
Journal of Information Technology Management ISSN #1042-1319 A Publication of the Association of Management IMPROVING IT PROJECT PORTFOLIO MANAGEMENT: LESSONS LEARNED KELD PEDERSEN DEPARTMENT OF POLITICAL
More informationThe profile of your work on an Agile project will be very different. Agile projects have several things in common:
The Agile Business Analyst IT s all about being Agile? You re working as a Business Analyst in a traditional project environment, specifying the requirements for IT Developers to build. Suddenly everyone
More informationThe role of the marketing department in Danish companies: Drivers for influence
42 nd EMAC Annual Conference Istanbul, June 2013 The role of the marketing department in Danish companies: Drivers for influence Suzanne C. Beckmann, Michala Jalving & Sarah Rohde Olsen Copenhagen Business
More informationORGANIZED FOR BUSINESS: BUILDING A CONTEMPORARY IT OPERATING MODEL
ORGANIZED FOR BUSINESS: BUILDING A CONTEMPORARY IT OPERATING MODEL Time is running out for the traditional, monopolistic IT model now that users have so many alternatives readily available. Today s enterprises
More informationHAMPTON UNIVERSITY ONLINE Hampton University School of Business PhD in Business Administration
Program Overview The PhD in Business Leadership and Administration is designed for professionals located nation wide who desire an advanced degree in business to excel in their careers. In addition, the
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 18-19 The Unified Process Static dimension Glossary UP (Unified
More informationpm4dev, 2007 management for development series Project Management Organizational Structures PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS
pm4dev, 2007 management for development series Project Management Organizational Structures PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology
More informationBasic Trends of Modern Software Development
DITF LDI Lietišķo datorsistēmu programmatūras profesora grupa e-business Solutions Basic Trends of Modern Software Development 2 3 Software Engineering FAQ What is software engineering? An engineering
More informationScaling Down Large Projects to Meet the Agile Sweet Spot
Scaling Down Large Projects to Meet the Agile Sweet Spot Philippe Kruchten Kruchten Engineering Services Ltd Presenter Philippe Kruchten, Ph. D., P. Eng. KESL 2906 West 37 th avenue Vancouver BC V5Z 2M9
More informationRISK MANAGMENT ON AN AGILE PROJECT
BIO PRESENTATION W3 6/28/ 11:30 AM RISK MANAGMENT ON AN AGILE PROJECT Michele Sliger Rally Software Development Better Software Conference June 26 29, Las Vegas, NV USA Michele Sliger Michele Sliger has
More informationExploring the directions and methods of business development. A comparative multiple-case study on Ikea and Vodafone
Exploring the directions and methods of business development A comparative multiple-case study on Ikea and Vodafone Michal Štefan Aalborg University Master thesis for MSc. in International Business Economics
More informationAgile Software Engineering Practice to Improve Project Success
Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems dietmar.winkler@qse.ifs.tuwien.ac.at
More informationBridging the IT Business Gap The Role of an Enterprise Architect
Whitepaper Bridging the IT Business Gap The Role of an Enterprise Architect Today s enterprises understand the value that Information Technology (IT) can bring to their business. IT supports day-to-day
More informationThe Truth About Agile Software Development with Scrum, The Facts You Should Know
The Truth About Agile Software Development with Scrum, The Facts You Should Know Copyright Notice of rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any
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 informationCSE 435 Software Engineering. Sept 16, 2015
CSE 435 Software Engineering Sept 16, 2015 2.1 The Meaning of Process A process: a series of steps involving activities, constraints, and resources that produce an intended output of some kind A process
More informationEMC PERSPECTIVE. Adopting an Agile Approach to OSS/BSS Development
EMC PERSPECTIVE Adopting an Agile Approach to OSS/BSS Development Reader ROI The agile software methodology is different from the traditional approach in that requirements gathering and analysis, design,
More informationManage projects effectively
Business white paper Manage projects effectively HP Project and Portfolio Management Center and HP Agile Manager Table of contents 3 Executive summary 3 The HP Solution Invest in what matters most then
More informationExpert Reference Series of White Papers. Intersecting Project Management and Business Analysis
Expert Reference Series of White Papers Intersecting Project Management and Business Analysis 1-800-COURSES www.globalknowledge.com Intersecting Project Management and Business Analysis Daniel Stober,
More informationImprove Information Governance Through Clarity and Collaboration
SAP Brief SAP s for Information Management SAP Information Steward and SAP PowerDesigner Objectives Improve Information Governance Through Clarity and Collaboration Collaborative approach to 360-degree
More informationHow To Adopt Rup In Your Project
08Bergstrom.C08 Page 127 Thursday, December 4, 2003 12:06 PM 8 How to Adopt RUP in Your Project Support Projects with Mentoring Make a High-Level Adoption Plan and Develop a Communication Plan Project
More informationIn today s acquisition environment,
4 The Challenges of Being Agile in DoD William Broadus In today s acquisition environment, it no longer is unusual for your program to award a product or service development contract in which the vendor
More informationHolistic Development of Knowledge Management with KMMM
1 Karsten Ehms, Dr. Manfred Langen Holistic Development of Knowledge Management with KMMM Siemens AG / Corporate Technology Knowledge Management & Business Transformation If knowledge management is to
More information