The use of objective oriented project planning tools for nanosafety and health concerns: a case study in nanomedicine research project

2016 ◽  
Vol 8 (4) ◽  
Author(s):  
Mohammad-Reza Nejadmoghaddam ◽  
Abdolreza Babamahmoodi ◽  
Arash Minai-Tehrani ◽  
Amir-Hassan Zarnani ◽  
Rassoul Dinarvand

AbstractPotential human health and environmental risks associated with nanoscience research projects and their deliverables, termed nanosafety, is one of the important issues for translating research findings into commercially viable products. This paper examined the applicability of project management tools to address nanosafety in an efficient manner. Using objectives oriented project planning (OOPP) we describe a new integrated content of the problem tree, the result tree, and the logical framework approach (LFA), by modeling our nanomedicine research project entitled “Nanomedicine preparation based on antibody drug conjugate (ADC)” as a case study. As a main result of the case study, we demonstrated an LFA matrix that highlights the need to deal with nanosafety as an activity of the research project. Consequently, the activity can lead to the output, standing operating procedure (SOP), for managing the project waste disposals and its deliverables side effects. In general, such output can be concluded as an important output for all nanoscience research projects to avoid underestimating risks for their nano-objects. Moreover, this article is written in the hope of providing an easy-to-understand template of project management tools for novice nanomedicine researchers who aim to apply OOPP in the design of their research projects.

2018 ◽  
Vol 3 (5) ◽  
pp. 174-187
Author(s):  
Said Abujudeh

The improvement of the project management forced the industrial organizations to focus on using the project management techniques in their industry, to plan and control the workflow to achieve their targets, further to increase the satisfaction of their customers. One of the most common project management tools are used is the work breakdown structure (WBS), which provide a framework for the implementation of the project scope including project planning, scheduling, monitoring, control, and estimation. Depending on the top-down approach the project activities will be broken into smaller parts that can be measured and controlled during the project implementation. The well-defined construction of the structure contributes to making the project more realistic and visual. However, the misunderstanding of the project WBS among the project team creates deflection and misinterpretation of the project scope. The main issue of this research is to improve the WBS of the installation plan and develop a standard WBS for plant installation. The research was limited to Asphalt plant installation WBS as a case study to identify the weaknesses of the current WBS at the case company which leads to extra installation time and cost. The research is offering a template WBS based on the company logic, defining the frequent risks that affect the plant installation based on the WBS and suggesting a suitable response strategy by recommending a control framework to monitor and control the WBS schedule throughout all installation phases.


2019 ◽  
Vol 8 (4) ◽  
pp. 325-344
Author(s):  
Trista Hollweck

PurposeThe purpose of this paper is to report on a qualitative case study that examined the potential benefits, challenges and implications of the mentor–coach (MC) role as a supportive structure for experienced teachers’ well-being and sense of flourishing in schools.Design/methodology/approachThe qualitative case study used data collected from surveys, interviews, focus groups and documentation. Data were coded and abductively analyzed using the “framework approach” with and against Seligman’s well-being PERMA framework. In order to include an alternative stakeholder perspective, data from a focus group with the district’s teacher union executive are also included.FindingsUsing the constituting elements of Seligman’s well-being (PERMA) framework, experienced teachers reported positive emotion, engagement, positive relationships, meaning and accomplishment from their MC experience. However, the MC role is not a panacea for educator well-being. Rather, the quality and effectiveness of the mentoring and coaching relationship is a determining factor and, if left unattended, negative experiences could contribute to their stress and increased workload.Research limitations/implicationsThe data used in this study were based on a limited number of survey respondents (25/42) and the self-selection of the interview (n=7) and focus group participants (n=6). The research findings may lack generalizability and be positively skewed.Originality/valueThis study contributes to the current lack of empirical research on the MC experience and considers some of the wider contextual factors that impact effective mentoring and coaching programs for educators.


2014 ◽  
Vol 21 (1) ◽  
pp. 94-106 ◽  
Author(s):  
Cenk Budayan ◽  
Irem Dikmen ◽  
M. Talat Birgonul

The importance of fit between an organization’s implementation of project management (PM), and its business level strategy is emphasized in the literature. However, there are a limited number of studies investigating the relationship between business level strategy and implementation of PM in the construction industry. This paper aligns one of the business strategies, namely differentiation, with the PM process. A framework representing differentiation in the construction industry is proposed in this study. Structural equation modelling (SEM) is used to validate the relationship between differentiation and the PM process. The results show that a relationship between differentiation strategy and PM exists. The two types of differentiation are revealed, namely “product variety and speed-related differentiation” (PSD) and “quality and image-related differentiation” (QID). The companies trying to differentiate based on PSD should focus on cost, time and quality management. Change management and project planning are identified as important drivers of differentiation based on PSD. On the other hand, the companies trying to differentiate on QID should consider health, safety and environmental issues as well as quality. Companies should also manage their resources effectively to support the PM process that in turn leads to successful differentiation. Companies can utilize the research findings as a guideline while formulating their differentiation strategies.


2011 ◽  
Vol 162 (4) ◽  
pp. 332-341
Author(s):  
Dorota KUCHTA

Classic project planning methods are summed up. It is shown that they are not suited for research projects and it is justified that a research project should be planned in a different way from the other ones. A review of methods from the literature is conducted – of the methods dedicated to research projects, but also of the methods dedicated to other types of projects biased by a high uncertainty and changeability degree. It is indicated how the latter might be applied to research projects. Further research directions are shown, which will allow one to work out planning methods for research projects adapted to their specificity. Attention is drawn to the fact that various types of research projects exist, while each type may potentially require a different planning method. The requirements set to research project plans by such institutions as the European Commission, the National Centre of Research and Development and the National Centre of Science are mentioned, and it is pointed out that these requirements should be changed in order to optimise the expenditure of financial resources earmarked for research.


2020 ◽  
Vol 1 (1) ◽  
pp. 35-50
Author(s):  
Irfan Uzzaman ◽  
Tasminur Mannan Adnan

DevOps, a cluster of tools to automate the tasks of building, testing and releasing the software, intends to optimize the end to end delivery lifecycle of software by eliminating the bottlenecks of each and every stage of development. This research paper presents the performance measure of different tools in the project planning and management phase of software development. Diverse tools exist for each and every phase of the development and depending on the outcome of the evaluation or selection criteria, tool with highest score is being chosen. This paper measures the performance of alternative project management tools viz. Jira, Trello, Leankit, AgileCraft based on these evaluation or selection criteria. To execute the underlying research work, a six-point scaling table is defined. The table measures the performance of project management automation tools and realizing their competence level score. This performance measure or the outcome as competence level score will be useful for the researchers or software developers to contemplate the best project management automation tool typically before making a decision about tool selection.


2009 ◽  
Vol 3 (5-6) ◽  
pp. 15-20 ◽  
Author(s):  
Judit Kiss ◽  
ZsoltT. Kosztyán

In case of using methodology of project planning, in the first step we had to create a “good” logic network. We had to determine the successors and predecessors of the tasks. However, usually successors and predecessors proceed from the technology, sometimes (especially in case of IT and innovation projects) these relations between tasks are not explicit. In case of projects, especially IT and innovation projects, one of the most critical points of view is the phase of logic planning. However, it is a very important phase, only slightly supported by any kind of Project Management tools. Our goal was to support the logic planning phase. In our paper a new planning method, namely SNPM (Stochastic Network Planning Method) is introduced through some practical applications. SNPM can determine all feasible solutions with the help of stochastic variables and can also take into consideration all possible precedents. The parameters of logic relations can be changed if the impacts on the project change. With this method the most probable project scenario can be determined taking into account costs and resource demands.


Author(s):  
Moshe Dayani ◽  
Roy Gelbard

The current research has two main objectives: 1) Integration of the system analyst's products together with the project manager's work, via handshaking of software tools used for these tasks (Software modeling tools, Project management tools, as well as Word and Excel files). 2) Simulation of the entire project's problem space subject to organization's policy and constraints in order to achieve best project planning in the given situation. For this purpose, a rule-based system, developed in this study, utilizes a simulation of entire project's problem-space, which is a Cartesian product composed of all system elements (as defined in the software modeling tool), and organization's policy, preferences and constraints, via a specific user interface (see Figure 1). Then the project manager can choose, by simple filtering, the appropriate planning, and the Gantt-chart and all plans' details are automatically exported to the Project Management tool.


2019 ◽  
Vol 19 (4) ◽  
pp. 17-25
Author(s):  
Deniz Özkan ◽  
Alok Mishra

Abstract Agile methodologies are becoming popular in software development. Managers are required to understand project’s progress and product quality without development documents. During Agile practices of the teams and organizations, Agile project management tools are frequently used. The use of such tools leads to achieving speed and efficiency, affects the quality of the software. The quality of final product is mostly related with to project management. Accordingly, the paper provides brief comparative perspective about the popular project management tools for agile projects. 16 popular Agile project management tools have been presented helping agile developers to plan and manage their tasks in an efficient manner. Taiga, Axosoft, Agielan, Planbox are more appropriate for start-up projects. The most twitted and most appreciated tools are reported as Jira, Trello, and VersionOne. SpiraTeam by Inflectra and Pivotal Tracker are other pricing and popular agile tools, providing flexibility to Agile developers and increase collaboration among team members.


Sign in / Sign up

Export Citation Format

Share Document