International Institute for Learning

APRIL 12, 2023

I remember getting my PMP back in 2002 and being instructed over and over to prevent changes from even being raised! Rubin Jen has been in the project management field for over 25 years; Spanning aerospace, engineering, telecom, software development, outsourcing, consulting, and government sectors.

Agile 59

Agile 2002 Telecoms Aerospace 59

Herding Cats

MARCH 17, 2019

Project Governance. Integrated Master Plan: The Foundation of Program Success , College of Performance Management, May 21, 2014. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Top Habits of Successful Project Managers.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

MAY 10, 2019

“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. 3, March 2002. 11 November 2002. 1, March 2014. 255, April 2010.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 11, 2017

Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46

2003 2014 2015 2011 46

Herding Cats

APRIL 16, 2019

Product Development (#ProdDev). Governance (#Governance). Agile Software Development (#ASD). Six Business System Rule - defines the assessment of the integrated business systems for Federal procurement and their integrity in providing information to the Government contracting office. . Strategy (#Strategy).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40