Search results

The purpose of this conceptual chapter is to highlight the disadvantages of project management to help the reader put project management work in context.

Different project management methodologies such as waterfall project management, Agile project management, Six Sigma, and Kanban are discussed in terms of overall problems and then specific problems with each methodology. Managing multiple projects and the problems with program and portfolio management are discussed.

The findings are that most formalized project management methods are ill-suited to most library-related situations. However, some aspects of project management are well suited to any project, at any size, and those are discussed.

The value of this paper is that readers will get a strong understanding of project management methodologies in context and a clear idea of the strengths and weaknesses of each.

This chapter takes a look at the future of project management. It starts with a historic view of the development of project management in the last five decades including the present. It shows that the role of the project manager has changed from an engineer manager to a business developer and a leader capable of dealing with multi-perspectives.

Projects are positioned in the context of changing organizational forms, including silo and network organizations. This leads to the conclusion that projects will play a key role in the future, especially in change management, business modeling, and value creation.

A section will discuss increased emphasis on learning and knowledge sharing, suggesting focus on the reflective and experimenting project manager, and planning as a social process.

A section will look at project management as a profession and point to the risk that the profession may become too narrow focusing on a well-defined body of knowledge. Current trends suggest that a broader view of projects be adopted including its strategic role and interplay with stakeholders, as has been discussed at length in this book.

We conclude the chapter by proposing a shift of paradigm.

The wide spread application of projects to many areas of society has led us to identify five generic elements that every project will have to address. They are: project management, project task, stakeholders, resources, and project environment. Each element will be further divided into five sub-elements. This five-by-five model will be used to identify the nature of a specific project and to develop appropriate approaches and means. It will also allow a circular planning process that gradually will lead to coherence among the five elements.

To illustrate the broad spectrum of projects that we see in practice, we have identified five types that will be characterized by the five-by-five model.

In view of the complex nature of most projects, the chapter will introduce four complementary perspectives: a technical, a business, an organizational, and a stakeholder perspective. Each perspective will describe key features of a project and is supported by theories, models, and methods. Although the perspectives are complementary, they are strongly interdependent.

The chapter will give an overview of the book.

Project management has become the hip new trend in librarianship, appearing more and more in job listings, position descriptions, and professional development offerings. How did project management become the latest buzzword, and what does it have to offer our profession?

The answers to these can be explored through a look at the evolution of project management from the concept of Scientific Management to the certifiable skill set it is today, and how that evolution connects with librarianship’s own changes over time. This examination is done through a literature and historical analysis.

A deeper look at the basic concepts behind project management in light of this historical and practical connection with librarianship demonstrates how project management not only can be a useful skill for library workers to embrace today, but will also illuminate how our service-oriented structure may not mesh well with a concept rooted in business and computing. However, libraries that take a systems approach to implementing project management may see that they are better able to find success.

This study is largely theoretical and based on literature and historical analysis rather than practical implementation and testing. However, it does offer us a different way of looking at a trendy concept, one which helps ground the concept in theory and practice in a way that is seldom done. It also provides examples of tools to help libraries implement project management with a systems approach, which has not been addressed much in library literature.

This chapter addresses issues of what should be done and when. Structuring of the project task into a number of activities is key to planning a course of action for a project. It involves combining two dimensions: when (the time) and what (relevant subject areas or work paths). Several examples will illustrate the issue.

The five-by-five model will be used to identify five parallel processes of a project: (1) task-oriented processes concerned with development of a solution, (2) organisational change processes focusing on understanding and accepting the change, (3) application and operational processes concerned with application and use of the project’s results, (4) environmental processes focusing on the interplay between the project and its environment including stakeholders, and (5) management processes dealing with activities in the middle box of the five-by-five model.

A number of models of the project’s course of action will be presented and discussed, e.g., a waterfall model, a parallel stream model based on the four perspectives introduced in Chapter 1, the course of actions as decisions and as a change process. Finally, we shall discuss Agile and Lean project management.

To demonstrate how the Project Management Body of Knowledge (PMBOK), a formal project management framework commonly used in corporate settings, can be used to manage library projects, even in situations where the librarian does not have authority over project resources, like personnel, scope, and budget.

This chapter uses a conceptual review of the library, project management, and library project management literature to construct recommendations and best practices.

Many of the PMBOK tools are effective for project managers working without formal authority. These tools include the Stakeholder Register, which allows a project manager to track stakeholders based upon their interest and influence; the Responsibility Assignment Matrix, which allows a project manager and team members to quickly and easily see work and personnel relationships; and Integrated Change Control, which provides project managers with a process for understanding and documenting the impact of project changes. These tools, as well as the PMBOK’s strategies on managing project communication and monitoring and controlling project work, which help orient stakeholders to the work and expectations of the project, while also making sure there are no surprises, provide effective project management tools for librarians working without formal authority.

While the PMBOK is occasionally discussed in the library literature, this chapter extensively uses the framework to connect the framework to library project management. This chapter also shows how the PMBOK, which relies on formal authority, can also be used in situations where the project manager lacks it.

This chapter explores the increasing use of Scrum, a project management framework used in software development, in libraries. This conceptual piece examines the advantages and disadvantages for a library profession to obtain training and professional certification for implementing Scrum.

Beginning with a brief literature review that surveys the use of Scrum and related frameworks in libraries, this chapter then provides a brief explanation of Scrum, the role of the ScrumMaster, and the certification process. An examination of the difficulties of project management in libraries leads to a discussion of the advantages of ScrumMaster certification for the library organization and the library professional, with caveats and alternatives.

Scrum offers lightweight methods to bring project management expertise to libraries lacking formal project management training. ScrumMaster certification is a quick and easy way to learn and implement the process, while offering professional advantages.

While the library literature has case studies of library professionals using Scrum and related Agile software development methodologies, this chapter looks at the ScrumMaster role in particular, the certification process, and the advantages for the organization and the professional.

This chapter brings to notice the general idea behind the need to consider value as a pertinent point since construction is swiftly moving towards sustainability. The introductory chapter introduces the general information about the subtopics across the parts of the book and mentions other techniques implemented in the construction industry. The value system for construction characterizes construction features into sections. The barriers often experienced in implementing value management highlight some of the difficulties encountered in applying value management or any new technique in the construction industry. The summary aspect ends the whole concept of the work discussed in this chapter.

Our notion of project control is based on the five-by-five model and constitutes a comprehensive control model including control of results, time and work control, resource control, financial control, and contract management.

The task of project control is determined by uncertainty and complexity and calls for improvisation and ingenuity in order to be able to maneuver the project. The notion of forward-oriented follow-up is introduced.