借鉴国外经验完善我国部门预算项目支出绩效评价机制

针对我国目前项目支出绩效评价中存在的问题，结合美国等西方国家在此方面的工作经验，提出了我国项目支出绩效评价制度应重点从建立科学的预算管理与政府会计制度，完善项目库管理和绩效评价相关法律法规；其次，提出应设立明确的管理机构，构建完善的项目支出绩效评价组织体系，制定科学的评价指标体系，完善项止支出绩效评价标准，制定有效的项目支出绩效评价计分方法，通过建立支出绩效评价信息系统，公开绩效评价结果，发挥人大的监督作用，加强对项国预算管理。通过以上几个方面的改革和完善，以期为我国完善部门预算项目支出绩教评价机制，全面评价政府治理绩效，提供有益的决策参考。     

基于过程的企业电子商务绩效评价模型

提出企业电子商务绩效评价是基于价值创造过程的动态评价,依据企业资源观（RBV）,从战略构建、资源分析、能力评估和绩效测量四个维度之间的因果作用关系构建电子商务绩效评价模型,采用结构方程验证模型的结构合理性和关联效应。基于模型建立了电子商务绩效评价指标体系,实现对价值产生的中间过程因素和关联作用关系的综合评价,通过我国75家制造企业电子商务绩效的实际测评,验证评价指标体系的可行性和有效性。     

北京市政府环境投资项目绩效审计评价指标体系框架研究

政府环境投资项目绩效审计是审计领域的新课题,本文选择北京市作为切入点研究政府环境投资项目绩效审计评价指标体系框架,涉及建立北京市政府环境投资项目绩效审计评价指标体系的范围、考虑的因素、指标体系框架等内容。指标设计力求定量与定性两方面结合。     

基于价值链的生产企业质量信用绩效评价研究

建立企业质量信用绩效评价体系对于提高产品质量安全具有非常重要的作用和意义。本文在借鉴相关研究成果的基础上,建立了企业质量信用管理的价值链模型,并以此模型为依据建立了企业质量信用管理绩效评价指标体系,应用模糊综合评价模型进行企业质量信用绩效综合评价。实例分析表明,通过这种方法,能够发现企业质量信用的贡献因素和制约因素,这将为企业质量信用管理的进一步发展提供决策支持。     

公共建设性投资项目绩效评价体系

本文首先分析了公共建设性投资项目绩效评价研究的背景:公共建设性投资项目的重要意义和绩效评价体系构建的必然性.其次阐述了公共建设性投资项目绩效评价体系存在的问题:绩效评价体系不完善;绩效评价的成果未充分利用;绩效评价的标准难以统一.针对这些问题提出了相应了解决措施:进一步完善公共建设性投资项目绩效评价体系;进一步加强对绩效成果的研究,充分利用绩效成果;进一步划分绩效评价的标准等.     

网络环境下企业技术创新绩效评价研究

按照网络环境下企业技术创新绩效评价的要求,本文首先分析和提出一套比较完整的网络环境下企业技术创新评价指标体系;在此基础上,利用人工神经网络建立网络环境下企业技术创新绩效的综合评价模型;最后,分析网络环境下影响企业技术创新绩效的主要因素,进一步为企业技术创新绩效管理提供依据。     

基于灰色关联度分析的发电企业组织绩效评价研究

企业的组织绩效评价问题一直是近年来理论界和实务界研究的一个热点问题,本文结合发电企业的人力资源和绩效管理特征,研究了发电企业组织绩效评价指标体系的构建,通过对指标的一致化与无量纲化处理,采用灰色关联度评价方法对发电企业组织绩效进行综合评判与比较、分析,为发电企业的组织绩效评价研究提供一种新思路、新方法。     

构建以企业价值最大化为导向的绩效评估体系

企业绩效评价体系，是指由一系列与绩效评价相关的评价制度、评价指标、评价方法、评价标准和评价机构等形成的有机整体。企业绩效评价体系由绩效评价制度体系、绩效评价组织体系和绩效指标体系三个子体系组成。企业绩效评价体系的科学实用性和可操作性是实现企业绩效客观、公正评价的前提。     

企业知识管理绩效的模糊评价模型与分析矩阵

在总结国内外知识管理绩效评价指标体系研究现状的基础上,提出应从过程和结果2个方面对知识管理绩效进行评价;建立了一套实用性较强的知识管理评价指标体系,并尝试用"模糊多级综合评价方法"对企业的知识管理绩效进行评价;指出了对评价得分进行分析的方法,并独创了过程-结果分析矩阵.     

不确定环境下医生绩效的评价方法

本文首先采用关键绩效指标法,构建了医生绩效评价的指标体系,针对指标存在的不确定性特点,应用证据推理算法,建立了医生绩效评价模型,有效地融合了定量和定性信息,对医生绩效进行了综合评估。结果表明,该方法解决了评价指标不确定性的问题,大大提高了评价的准确性。可得结论,证据推理算法应用于医生绩效评价具有一定的可行性、实用性和推广价值。     

软件外包项目复杂性下的交互记忆系统与知识转移

针对软件外包项目团队中如何有效知识转移问题,构建交互记忆系统、项目复杂性和知识转移绩效之间关系的概念模型,基于25家软件外包承接企业中107个软件外包团队的问卷调查数据,运用偏最小二乘法对数据进行分析。研究结果表明,专长度和可信度对团队知识转移绩效和协调度有显著的正向影响,软件外包项目结构复杂性对专长度与知识转移绩效的关系有显著的正向调节作用,软件外包项目动态复杂性对专长度与知识转移绩效的关系有显著的负向调节作用。研究结果揭示了项目复杂性条件下交互记忆系统与知识转移绩效之间的作用机理,推进了软件外包知识转移理论发展,并为软件外包团队有效地进行知识转移提供管理启示。     

Managing Outsourced Software Projects: An Analysis of Project Performance and Customer Satisfaction

We examine the drivers of project performance and customer satisfaction in outsourced software projects using a proprietary panel dataset. The data cover 822 customer observations related to 182 unique projects executed by an India‐based software services vendor. Adopting a multidisciplinary perspective, we investigate how project planning, team stability, and communication effectiveness impact project performance and customer satisfaction. We delineate the direct and interactive influences of the antecedent variables. We also examine how these influences are moderated by two important project contexts: (a) the nature of software work (maintenance and development vs. testing projects) and (b) project maturity (new vs. mature projects). Among other results, we demonstrate that, when project planning capabilities are high, the positive impact of team stability and communication effectiveness on project performance is even higher. In addition, our results suggest that the impact of communication on project performance is muted when team stability is high. Finally, we also demonstrate that the impact of the antecedent variables on project performance varies with the nature of software work. Our findings offer specific and actionable insights to managers that can help them manage outsourced projects better, and open up new research perspectives in the context of outsourced project management.     

软件项目风险的神经网络预测模型

选择神经网络方法建立模型,模型的输入部分是经验证的64个风险因素,输出部分是软件项目的总体产出.首先验证模型输入输出部分的内容有效性,然后收集软件组织的实际软件项目样本用于建立和验证模型.实验结果表明,该模型能有效地测量软件项目的总体风险.     

建筑工程项目管理软件的发展方向-4D建模及应用

本文从现有项目管理软件的功能分析入手,找出现有项目管理软件功能与实际需求的差距,论述了基于4D模型的项目管理软件是其发展方向,提出了基于4D模型的项目管理软件的开发事例。     

基于CMM与OPM3的软件项目关键成功因素分析

本文在对软件项目管理和项目管理成熟度模型发展讨论的基础上,根据中国项目项目管理知识体系以及我国软件企业中软件项目管理和软件能力成熟度模型的发展中所出现的问题,总结和归纳了影响软件项目管理的31个关键影响因素,建立了软件项目管理三层次模型。通过对软件项目管理人员以调查问卷的形式收集数据资料,利用因子分析验证了软件项目管理三层次模型的正确性和可行性,以期通过软件项目管理提高我国软件企业CMM等级。     

Value‐Driven Creation of Functionality in Software Projects: Optimal Sequencing and Reuse

We study the problem of optimally sequencing the creation of elements in a software project to optimize a time‐weighted value objective. As elements are created, certain parts of the system (referred to as “groups”) become functional and provide value, even though the entire system has not been completed. The main tradeoff in the sequencing problem arises from elements that belong to multiple groups. On the one hand, creating groups with common elements early in the project reduces the effort required to build later functionality that uses these elements. On the other hand, the early creation of such groups can delay the release of some critical functionality. We formulate the element sequencing problem and propose a heuristic to solve it. This heuristic is compared against a lower bound developed for the problem. Next, we study a more general version of the element sequencing problem in which an element requires some effort to be made reusable. When a reusable element is used in another group, some more effort is needed to specialize the element to work as desired in that group. We study reuse decisions under a weighted completion time objective (i.e., the sum of the completion time of each group weighted by its value is minimized), and show how these decisions differ from those under a traditional makespan objective (i.e., only the final completion time of the project is minimized). A variety of analytical and numerical results are presented. The model is also implemented on data obtained from a real software project. A key finding of this work is that the optimal effort on reuse is never increased (typically lowered) when a weighted completion time objective is used. This finding has implications for managing reuse in projects in which user value influences the order in which functionality is created.     

Optimal Coordination in Distributed Software Development

The construction of a software system requires not only individual coding effort from team members to realize the various functionalities, but also adequate team coordination to integrate the developed code into a consistent, efficient, and bug‐free system. On the one hand, continuous coding without adequate coordination can cause serious system inconsistencies and faults that may subsequently require significant corrective effort. On the other hand, frequent integrations can be disruptive to the team and delay development progress. This tradeoff motivates the need for a good coordination policy. Both the complexity and the importance of coordination is accentuated in distributed software development (DSD), where a software project is developed by multiple, geographically‐distributed sub‐teams. The need for coordination in DSD exists both within one sub‐team and across different sub‐teams. The latter type of coordination involves communication across spatial boundaries (different locations) and possibly temporal boundaries (different time zones), and is a major challenge that DSD faces. In this study, we model both inter‐ and intra‐sub‐team coordination in DSD based on the characteristics of the systems being developed by the sub‐teams, the deadline for completion, and the nature of division adopted by the sub‐teams with respect to development and integration activities. Our analysis of optimal coordination policies in DSD shows that integration activities by one sub‐team not only benefit that sub‐team (as is the case in co‐located development) but can also help the other sub‐teams by providing greater visibility, thereby resulting in a higher integration frequency relative to co‐located development. Analytical results are presented to demonstrate how the characteristics of the projects and the sub‐teams, and the efficiency of communication across the sub‐teams, affect coordination and productivity. We also investigate the pros and cons of using specialized integration sub‐teams and find that their advantage decreases as the project schedule becomes tighter. Decentralized decisions and asymmetric subsystems are also discussed.     

Team Dispersion,Information Technology,and Project Performance

The impact of information technology (IT) on the performance of distributed projects is not well understood. Although prior research has documented that dispersion among project teams has an adverse effect on project performance, the role of IT as an enabler of communication to bridge the spatial distance among team members in distributed networks has not been empirically studied. We focus on the role of IT as a moderator of the relationship between team dispersion and project performance using projects as the unit of analysis. We find that IT mitigates the negative effect of team dispersion on project performance, especially in high information volume projects. Our central contribution is the development of an empirically tested model to improve the understanding of the operational impact of IT as a vehicle to bridge spatial dispersion among distributed teams that are engaged in knowledge‐intensive work.     

基于活动敏感性的动态缓冲监控方法研究

缓冲监控问题对于企业成功应用关键性项目管理,提高项目进度管理绩效和确保项目按时完工,都至关重要。本文针对现有缓冲监控方法在项目进度监控中所存在的忽视内部情况的问题,引入项目进度风险分析方法中的活动敏感性信息。研究了动态环境下活动敏感性指标的计算和监控阀值的设定,在缓冲的黄区监控中集成了考虑活动敏感信息的动态监控过程。在综合考虑缓冲指标和活动关联度指标的监控指标体系,综合设置各指标的监控阀值的基础上,提出了基于活动敏感性信息的关键链动态缓冲监控方法。最后通过一个算例将所提方法与现有方法进行比较,实验结果表明,合理设置活动关联度的监控阀值后,所提方法在总赶工时间、总赶工活动数、超计划完工次数以及监控负荷这四个绩效方面的结果更优。     

Application Development Using Fault Data

We develop a general model for software development process and propose a policy to manage system coordination using system fault reports (e.g., interface inconsistencies, parameter mismatches, etc.). These reports are used to determine the timing of coordination activities that remove faults. We show that under an optimal policy, coordination should be performed only if a “threshold” fault count has been exceeded. We apply the policy to software development processes and compare the management of those projects under different development conditions. A series of numerical experiments are conducted to demonstrate how the fault threshold policy needs to be adjusted to changes in system complexity, team skill, development environment, and project schedule. Moreover, we compare the optimal fault threshold policy to an optimal release‐based policy. The release‐based policy does not take into account fault data and is easier to administer. The comparisons help to define the range of project parameters for which observing fault data can provide significant benefits for managing a software project.