Information technology project management practices effectively help organizations achieve IT value. We employed a semistructured review with the practice of jizhuanti by tracing the development of the research intersection of IT and projects through the works of seven influential authors. From the analysis of the review, we build representative models of the intersection and suggest open lines of research. The results unveil stakeholder integration, knowledge management, and risk controls as principal themes for the sampling subset. Future scholars can continue to delve into these areas over more complex systems, consider other categories, or open new directions revealed by practice.
BarkiH.HartwickJ. (1989). Rethinking the concept of user involvement. MIS Quarterly, 13(1), 53–63.
3.
BarkiH.HartwickJ. (1994a). Measuring user participation, user involvement, and user attitude. MIS Quarterly, 18(1), 59–82.
4.
BarkiH.HartwickJ. (1994b). User participation, content, and conflict-resolution: The mediating roles of influence. Information Systems Research, 5(4), 422–438.
5.
BarkiH.RivardS.TalbotJ. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203–225.
6.
BassellierG.BenbasatI.ReichB. H. (2003). The influence of business managers’ IT competence on championing IT. Information Systems Research, 14(4), 317–336.
7.
BrynjolfssonE. (1993). The productivity paradox of information technology. Communications of the ACM, 36(12), 66–77.
8.
ChangJ. Y.JiangJ. J.KleinG.WangE. T. (2019). Enterprise system programs: Goal setting and cooperation in the integration team. Information & Management, 56(6), 103–137.
9.
ChangJ. Y.JiangJ. J.KleinG.WangE. T. G. (2014). Do too many goals impede a program? A case study of enterprise system implementation with multiple interdependent projects. Information & Management, 51(4), 465–478.
10.
ChangK.SheuT. S.KleinG.JiangJ. J. (2010). User commitment and collaboration: Motivational antecedents and project performance. Information and Software Technology, 52(6), 672–679.
11.
ChangJ. Y.WuX.DiscenzaR.KleinG. (2022). Creative software development with team boundary management. Journal of Computer Information Systems, 62(4), 694–705.
12.
de GuineaA. O.ParéG. (2017). What literature review type should I conduct?The Routledge companion to management information systems (pp. 73–82). Routledge.
13.
DingsøyrT.MoeN. B.SeimE. A. (2018). Coordinating knowledge work in multiteam programs: Findings from a large-scale agile development program. Project Management Journal, 49(6), 64–77.
14.
FernandezW.KleinG.JiangJ.KhanR. M. (2022). Integration networks in IT-enabled transformation programs. International Journal of Managing Projects in Business, 15(6), 913–937.
15.
GeminoA.ReichB. H.SauerC. (2007a). A temporal model of information technology project performance. Journal of Management Information Systems, 24(3), 9–44.
16.
GeminoA.ReichB. H.SauerC. (2015). Plans versus people: Comparing knowledge management approaches in IT-enabled business projects. International Journal of Project Management, 33(2), 299–310.
17.
GeminoA.SauerC.ReichB. H. (2010). Using classification trees to predict performance in information technology projects. Journal of Decision Systems, 19(2), 201–223.
18.
GeminoA. C.ReichB. H.SauerC. (2007b, December). Beyond chaos: Examining IT project performance. Paper presented at the 2nd International Research Workshop on Information Technology Project Management (IRWITPM), Montréal, Québec, Canada.
19.
GrantR. M. (1996). Toward a knowledge-based theory of the firm. Strategic Management Journal, 17(S2), 109–122.
20.
GregoryR. W.BeckR.KeilM. (2013). Control balancing in information systems development offshoring projects. MIS Quarterly, 37(4), 1211–1232.
21.
GregoryR. W.KeilM. (2014). Blending bureaucratic and collaborative management styles to achieve control ambidexterity in IS projects. European Journal of Information Systems, 23(3), 343–356.
22.
GregoryR. W.KeilM.MuntermannJ.MähringM. (2015). Paradoxes and the nature of ambidexterity in IT transformation programs. Information Systems Research, 26(1), 57–80.
23.
HartwickJ.BarkiH. (1994). Explaining the role of user participation in information-system use. Management Science, 40(4), 440–465.
24.
HsuJ. S.LiangT.WuS. P.KleinG.JiangJ. J. (2011). Promoting the integration of users and developers to achieve a collective mind through the screening of information system projects. International Journal of Project Management, 29(5), 514–524.
25.
JiangJ. J.ChangJ. Y.ChenH.-G.WangE. T.KleinG. (2014). Achieving IT program goals with integrative conflict management. Journal of Management Information Systems, 31(1), 79–106.
26.
JiangJ. J.KleinG.BallounJ. (1996). Ranking of system implementation success factors. Project Management Journal, 27(4), 49–53.
27.
JiangJ. J.KleinG.ChangJ. Y. (2019). Teamwork behaviors in implementing enterprise systems with multiple projects: Results from Chinese firms. Journal of Systems and Software, 157, 110392.
28.
JiangJ. J.KleinG.ChenH. G. (2006). The effects of user partnering and user non-support on project performance. Journal of the Association for Information Systems, 7(1), 68–90.
29.
JiangJ. J.KleinG.DiscenzaR. (2001). Information system success as impacted by risks and development strategies. IEEE Transactions on Engineering Management, 48(1), 46–55.
30.
JiangJ. J.KleinG.EllisT. S. (2002). A measure of software development risk. Project Management Journal, 33(3), 30–41.
31.
JiangJ. J.KleinG.FernandezW. D. (2018a). From project management to program management: An invitation to investigate programs where IT plays a significant role. Journal of the Association for Information Systems, 19(1), 40–57.
32.
JiangJ. J.KleinG.MargulisS. (1998). Important behavioral skills for IS project managers: The judgments of experienced IS professionals. Project Management Journal, 29(1), 39–43.
33.
JiangJ. J.KleinG.TsaiJ. C.-A.LiY. (2018b). Managing multiple-supplier project teams in new software development. International Journal of Project Management, 36(7), 925–939.
34.
KeilM. (1995). Pulling the plug: Software project management and the problem of project escalation. MIS Quarterly, 19(4), 421–447.
35.
KeilM.CuleP. E.LyytinenK.SchmidtR. C. (1998). A framework for identifying software project risks. Communications of the ACM, 41(11), 76–83.
36.
KeilM.LeeJ. S.MähringM. (2020). IT project management. MIS Quarterly Curation.
37.
KeilM.MannJ.RaiA. (2000a). Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Quarterly, 24(4), 631–664.
38.
KeilM.RaiA.LiuS. (2013). How user risk and requirements risk moderate the effects of formal and informal control on the process performance of IT projects. European Journal of Information Systems, 22(6), 650–672.
39.
KeilM.SmithH. J.IacovouC. L.ThompsonR. L. (2014a). The dynamics of IT project status reporting: A self-reinforcing cycle of distrust. Journal of the Association for Information Systems, 15(12), 879–912.
40.
KeilM.SmithH. J.IacovouC. L.ThompsonR. L. (2014b). The pitfalls of project status reporting. MIT Sloan Management Review, 55(3), 57–64.
41.
KeilM.TanB. C.WeiK.-K.SaarinenT.TuunainenV.WassenaarA. (2000b). A cross-cultural study on escalation of commitment behavior in software projects. MIS Quarterly, 24(2), 299–325.
42.
KirschL. J. (1996). The management of complex tasks in organizations: Controlling the systems development process. Organization Science, 7(1), 1–21.
43.
KirschL. S. (1997). Portfolios of control modes and IS project management. Information Systems Research, 8(3), 215–239.
44.
KirschL. J. (2004). Deploying common systems globally: The dynamics of control. Information Systems Research, 15(4), 374–395. doi:10.1287/isre.1040.0036
45.
KirschL. J.SambamurthyV.KoD. G.PurvisR. L. (2002). Portfolios of control modes and IS project management. Management Science, 48(4), 484–498.
46.
KirschL. J.SlaughterS. A. (2013). Managing the unmanageable: How IS research can contribute to the scholarship of cyber projects. Journal of the Association for Information Systems, 14(4), 198–214.
47.
KleinG.JiangJ. J.TeschD. B. (2002). Wanted: Project teams with a blend of IS professional orientations. Communications of the ACM, 45(6), 81–87.
48.
KleinG.MüllerR. (2020). Literature review expectations of Project Management Journal®. SAGE Publications.
49.
KoD.-G.KirschL. J.KingW. R. (2005). Antecedents of knowledge transfer from consultants to clients in enterprise system implementations. MIS Quarterly, 29(1), 59–85.
50.
LeeH. K.LeeJ. S.KeilM. (2018). Using perspective-taking to de-escalate launch date commitment for products with known software defects. Journal of Management Information Systems, 35(4), 1251–1276.
51.
LeeJ. S.KeilM.KasiV. (2012). The effect of an initial budget and schedule goal on software project escalation. Journal of Management Information Systems, 29(1), 53–78.
52.
LeeJ. S.KeilM.ShalevE. (2019). Seeing the trees or the forest? The effect of IT project managers’ mental construal on IT project risk management activities. Information Systems Research, 30(3), 1051–1072.
53.
LeiY.WuX.JiangJ. (in press). Shared mental models and boundary management activities in new product development: A perspective on multiteam systems. IEEE Transactions on Engineering Management. DOI: 10.1109/TEM.2022.3147905
54.
LiuJ. M. (2009). A summary of studies on ancient Chinese jizhuanti. Journal of Hubei Normal University (Philosophy and Social Sciences), 29(5), 535–542.
55.
LiuJ. Y.-C.ChenH. H.-G.JiangJ. J.KleinG. (2010a). Task completion competency and project management performance: The influence of control and user contribution. International Journal of Project Management, 28(3), 220–227.
56.
LiuS.ZhangJ.KeilM.ChenT. (2010b). Comparing senior executive and project manager perceptions of IT project risk: A Chinese Delphi study. Information Systems Journal, 20(4), 319–355.
57.
MähringM.KeilM. (2008). Information technology project escalation: A process model. Decision Sciences, 39(2), 239–272.
58.
MontealegreR.KeilM. (2000). De-escalating information technology projects: Lessons from the Denver International Airport. MIS Quarterly, 24(3), 417–447.
59.
NannetteP. N.KeilM.TanF. B. (2009). IT project managers’ construction of successful project management practice: A repertory grid investigation. Information Systems Journal, 19(3), 255–282.
60.
ParoliaN.ChenJ. V.JiangJ. J.KleinG. (2015). Conflict resolution effectiveness on the implementation efficiency and achievement of business objectives in IT programs: A study of IT vendors. Information and Software Technology, 66(2015), 30–39.
61.
ParoliaN.JiangJ. J.KleinG. (2013). The presence and development of competency in IT programs. Journal of Systems and Software, 86(12), 3140–3150.
62.
PouloudiN.CurrieW.WhitleyE. A. (2016). Entangled stakeholder roles and perceptions in health information systems: A longitudinal study of the UK NHS N3 network. Journal of the Association for Information Systems, 17(2), 107–161.
63.
ReichB.GeminoA.SauerC. (2007, June). Myths about information technology project performance? Proceedings of the ASAC Conference, Ottawa, Canada.
64.
ReichB. H. (2007). Managing knowledge and learning in IT projects: A conceptual framework and guidelines for practice. Project Management Journal, 38(2), 5–17.
65.
ReichB. H.GeminoA.SauerC. (2012). Knowledge management and project-based knowledge in IT projects: A model and preliminary empirical results. International Journal of Project Management, 30(6), 663–674. doi:10.1016/j.ijproman.2011.12.003
66.
ReichB. H.GeminoA.SauerC. (2014). How knowledge management impacts performance in projects: An empirical study. International Journal of Project Management, 32(4), 590–602. doi:10.1016/j.ijproman.2013.09.004
67.
SchmidtR.LyytinenK.KeilM.CuleP. (2001). Identifying software project risks: An international Delphi study. Journal of Management Information Systems, 17(4), 5–36.
68.
SlaughterS. A.KirschL. J. (2006). The effectiveness of knowledge transfer portfolios in software process improvement: A field study. Information Systems Research, 17(3), 301–320. doi:10.1287/isre.1060.0098
69.
SnowA. P.KeilM. (2002). A framework for assessing the reliability of software project status reports. Engineering Management Journal, 14(2), 20–26.
70.
StockdaleR.StandingC. (2006). An interpretive approach to evaluating information systems: A content, context, process framework. European Journal of Operational Research, 173(3), 1090–1102.
71.
SwansonE. B. (1974). Management information systems: Appreciation and involvement. Management Science, 21(2), 178–188.
72.
TeschD.SobolM. G.KleinG.JiangJ. J. (2009). User and developer common knowledge: Effect on the success of information system development projects. International Journal of Project Management, 27(7), 657–664. doi:10.1016/j.ijproman.2009.01.002
73.
TiwanaA. (2008). Do bridging ties complement strong ties? An empirical examination of alliance ambidexterity. Strategic Management Journal, 29(3), 251–272.
74.
TiwanaA. (2009). Governance-knowledge fit in systems development projects. Information Systems Research, 20(2), 180–197.
75.
TiwanaA. (2010). Systems development ambidexterity: Explaining the complementary and substitutive roles of formal and informal controls. Journal of Management Information Systems, 27(2), 87–126.
76.
TiwanaA.KeilM. (2009). Control of internal and outsourced software projects. Journal of Management Information Systems, 26(3), 9–44.
77.
TiwanaA.McLeanE. R. (2005). Expertise integration and creativity in information systems development. Journal of Management Information Systems, 22(1), 13–43.
78.
TsaiJ. C. A.JiangJ. J.KleinG.HungS. Y. (in press, a). Task conflict resolution in the design of legacy replacement systems. Journal of Management Information Systems.
79.
TsaiJ. C. A.KleinG.SaundersC. S.JiangJ. J. (in press, b). Information elaboration and coopetition: Participation in the replacement of legacy systems. IEEE Transactions on Engineering Management. DOI: 10.1109/TEM.2022.3185626
80.
TsaiJ. C.A.WuX.KleinG.JiangJ. J. (2021). Goal equivocality and joint account of meaning creation in an enterprise system program. Information Systems Management, 39(1), 82–97. doi:10.1080/10580530.2021.1879324
81.
WallaceL.KeilM.RaiA. (2004a). How software project risk affects project performance: An investigation of the dimensions of risk and an exploratory model. Decision Sciences, 35(2), 289–321.
82.
WallaceL.KeilM.RaiA. (2004b). Understanding software project risk: A cluster analysis. Information & Management, 42(1), 115–125.
83.
WangE. T. G.ChangJ. Y. T.JiangJ.-Y. J.KleinG. (2011). User advocacy and information system project performance. International Journal of Project Management, 29(2), 146–154.
84.
WuX. J.HuangW. W.TsaiJ. C. A.KleinG.JiangJ. J. (2020a). Differentiation and dynamism within the IT development program. Journal of Management Science and Engineering, 5(3), 150–161.
85.
WuX.HuangW.JiangJ.KleinG.LiuS. (2020b). Boundary buffering: Limiting interference and information leakage in design teams. International Journal of Operations & Production Management, 40(3), 293–313.
86.
WuX.JiangR.TsaiJ. C.KleinG. (in press, a). Shared mental models in multiteam systems: Improving enterprise system implementation. International Journal of Managing Projects in Business.
87.
WuX.KleinG.JiangJ. (in press, 2023b). On the road to digital transformation: A literature review of IT program management. Project Management Journal, 54(4).
88.
YeowA.SohC.HansenR. (2018). Aligning with new digital strategy: A dynamic capabilities approach. The Journal of Strategic Information Systems, 27(1), 43–58.
