Rebel’s Guide to PM

JANUARY 28, 2022

This brainstorming element normally falls outside of the traditional project management role, but is more prevalent in software projects, when engineers have a free reign to come up with new ideas and then have to see them through. This review first appeared on the blog in 2009. It’s the book I wish I had written.

Software Review 195

Software Review Technical Review Underperforming Technical Team 2009 195

The IIL Blog

FEBRUARY 21, 2024

Before you can harness the power of AI, you need access to software and data. Let’s start with software. An API allows you to connect your software with external AI services. An API allows you to connect your software with external AI services. For example, Jira, Trello, Asana, and Smartsheet all have connectors.

Artificial Inteligence 78

Artificial Inteligence ChatGPT Generative AI 2009 78

Scrum.org

DECEMBER 18, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The Scrum Guide” by Ken Schwaber and Jeff Sutherland (2009, 2010).

2010 232

2010 SCRUM 2002 2004 232

Rebel’s Guide to PM

OCTOBER 30, 2018

Jack Risos obtained his PMP certificate in 2009. He has delivered software and business transition projects in the banking, insurance, software, and manufacturing industries. He’s also qualified in instructional design and adult education, which is handy, as it means he understands how to put training material together.

Software Review 253

Software Review 2009 Manufacturing Certification 253

Scrum.org

FEBRUARY 3, 2023

Scrum started as an iterative and incremental approach for software product development. Scrum Guide May of 2009: Sprints deliver an increment of the final product that is potentially releasable. The answer is both historical and essential.

2009 186

2009 2020 Software Review SCRUM 186

Rebel’s Guide to PM

NOVEMBER 12, 2018

Susan Stamm: Superstar Press, 2009. Collaboration Explained: Facilitation Skills for Software Project Leaders. Scott Berkun: O’Reilly Media, 2009. Very useful and highly recommended. 42 Rules of Employee Engagement. ISBN: 9780979942884. It includes lots of stories to illustrate the points and it’s easy to read.

2013 292

2013 2009 2011 2006 292

LiquidPlanner

MAY 24, 2022

In the long-term, a structured and consistent approach offered by dedicated software platforms will provide your teams access to big datasets, taking the guesswork out of risk management and reducing your assumption to knowledge ratio. Butrico, Risk: A User’s Guide, New York: Portfolio, 2021. McGrath and I.

Risk Management 158

Risk Management Risk 2003 2007 158

Rebel’s Guide to PM

OCTOBER 4, 2021

The most recent version was released in June 2009, which has split the manual into two, covering project managers and project sponsors. What are the most used tools and software on PRINCE2? PRINCE2 doesn’t mandate tools and software, you can use whatever you like – or nothing at all. No, not that I’m aware of.

Prince2 422

Prince2 Underperforming Technical Team Certification PMI 422

Scrum.org

AUGUST 1, 2022

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). Analysis of fault generation caused by stress during software development.

2004 242

2004 2010 2009 2016 242

Epicflow Blog

JULY 22, 2021

A lot of planning is performed by project management software these days, which allows PMs to improve the quality of this important stage of the project implementation. . There is one more important component to the successful work of a project manager: utilization of smart software tools. Organizing. References.

2009 98

2009 Software Review Technical Review PMI 98

Project Pulse Journal

OCTOBER 7, 2023

Defining Quantitative Risk Analysis Quantitative risk analysis is an approach that leverages numerical values and calculations to identify, measure, and manage potential risks associated with a given project or decision (Meredith & Mantel, 2009; Kerzner, 2017). Meredith & Mantel, 2009). References: Meredith, J. Kerzner, H.

Risk 52

Risk 2009 2023 2017 52

Scrum.org

JUNE 1, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. Forsyth, 2009 or Brown, 2019)? Similarly, I’ve also experienced one software team where every member was contractually responsible for a different product. Festinger, L.

SCRUM 225

SCRUM 2007 2003 2006 225

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Don't hear one?

Software Developers 46

Software Developers Software Development Estimate 2006 46

Scrum.org

JULY 24, 2023

Learn more : Gojko Adzic: “Impact Mapping: Making a big impact with software products and projects,” 2009. Use it to ensure everyone understands and agrees on the goals and how to achieve them, reducing the risk of building something that doesn’t contribute to the desired outcomes.

SCRUM 170

SCRUM Lean Innovation 2020 170

Digite

JANUARY 7, 2018

This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work. By David J Anderson. By Mike Burrows.

Lean 79

Lean Software Review 2010 2014 79

International Institute for Learning

JULY 7, 2022

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). 2009), include eXtreme Programming (XP) (Beck and Fowler, 2001) and Scrum (Schwaber and Beedle, 2002).

Innovation 59

Innovation Agile 2002 2001 59

Gunther Verheyen

DECEMBER 17, 2020

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141

2010 SCRUM 2002 2004 141

Rebel’s Guide to PM

SEPTEMBER 21, 2016

I declared 2009 the year of the Office Goddess and I wrote a series of posts about how to excel at work. For more up-to-date software reviews, see my complete list here. And also the massive shopping centre. This was one of my favourites: about Pareto and the 80/20 rule and how some stuff just needs to get done.

2007 150

2007 2009 2008 2010 150

International Institute for Learning

JANUARY 18, 2023

For this project there are two main deliverables, the bulletin boards and the software that manages and displays the information. The development approach might look like this: Software works well with iterative or incremental development approaches where you can experiment, receive feedback, and make changes. Bulletin Board.

Cadence 52

Cadence 2009 Innovation 2018 52

Scrum.org

MARCH 16, 2020

I believe Agile software development is more than ready to use new forecasting techniques to express uncertainy to narrow their decision-making process. I believe we can use this definition in Agile software development. Forecasting in Agile software development. The decade in front of us.

Agile 209

Agile Underperforming Technical Team 2030 Estimate 209

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Increasing the Probability of Success , Dallas MPUG, May 6th, 2009.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

JANUARY 20, 2018

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). The presidents are always dead presidents.

Software 38

Software 2006 Software Developers Software Development 38

Proofhub

OCTOBER 13, 2020

million people in the UK worked from home in the UK (compared to just 884,000 in 2009). Here’s a list of recommended remote working tools to get you started: ProofHub : Online project management software that serves as an all-encompassing virtual office for remote teams. According to Forbes , more than 1.54

Infrastructure 127

Infrastructure 2009 2008 Software Review 127

The IIL Blog

MAY 17, 2023

Systems development projects, especially those with a large software component, would spend years gathering requirements, designing, and building a system that would be plagued by changes and completely outdated by the time it was launched. They walked away with a shared set of values and principles that are documented in the Agile Manifesto.

Aerospace 147

Aerospace Technical Review Underperforming Technical Team Governance 147

Scrum.org

JULY 26, 2023

Mehr erfahren : Gojko Adzic: “Impact Mapping: Making a big impact with software products and projects,” 2009. So verringern Sie das Risiko, etwas zu bauen, das nicht zu den gewünschten Ergebnissen beiträgt.

SCRUM 137

SCRUM Lean Innovation 2020 137

Scrum.org

MAY 29, 2020

A year later, in 2000, Kent Beck published another book called “ Test Driven Development by Example ” and explains Test Driven Development (TDD) is a software process and not about writing tests before the code with one more important aspect – refactoring. The following is the sequence given in his book: -. Add a test.

Software Review 139

Software Review Technical Review 2004 2003 139

Project Pulse Journal

NOVEMBER 14, 2023

Resources include human resources (specific skill sets), equipment, software, locations, and budgets. Cost management explores all potential expenses, including staffing costs, software licenses, materials, etc. Once identified, the allocation of resources is spread across the project timeline, ensuring optimal utilization.

Planning 52

Planning 2017 Risk Management 2009 52

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 5887, 2009. Software Engineering Institute, January 1996. 5, September/October 2011.

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. 5887, 2009.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Productivity Land

OCTOBER 25, 2023

The Crypto Landscape in 2023 Cryptocurrencies have come a long way since the inception of Bitcoin in 2009. Develop and Test Your Product If your crypto business involves developing software or technology, work on creating a functional prototype or minimum viable product (MVP).

2023 52

2023 Technical Review Finance Innovation 52

Epicflow Blog

JULY 29, 2019

For managing these projects, consider new PM software like Epicflow , which is designed specifically for managing several projects simultaneously. That’s because Epicflow software is designed for managing several projects simultaneously. Read more: Why Multi-Project Management Is Becoming a Necessity. Critical Thinking and Analysis.

2022 91

2022 Artificial Inteligence PMI Innovation 91

Herding Cats

SEPTEMBER 25, 2018

7] "Decision Making Under Uncertainty: Think Clearly, act Decisively and Feel Confident - Unilever's Story," Sven Roden, 2009 Palisade Conference, Risk Analysis, Applications, and Training, 21-22 October 2009. . Making a proxy attribute, when a natural attribute is available.

2009 34

2009 Artificial Inteligence 2013 2005 34

Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

International Institute for Learning

MARCH 29, 2023

Product owners typically work in product development, especially with digital and software projects. A project manager may be accountable for the overall project but work with a Scrum Master for a software deliverable. The Product Owner The Product Owner is the person accountable for the performance of a product.

SCRUM 52

SCRUM Leadership Governance Government 52

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What factors lead to software project failure?” All for the want of a nail.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

OCTOBER 15, 2017

I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. Here's a sampling of background on how agile software development processes are used in a domain where life is at stake.

Process 39

Process Agile 2011 Aerospace 39