Scrum.org

SEPTEMBER 3, 2019

In his book, “Drive,” Daniel Pink talks about what makes a motivated employee, and he boils it down to three things: Autonomy — the art of self-organization and having some semblance of control over your surroundings. So, what does this mean for a software development organization? Instill a sense of purpose. McLeod, S.A.

Agile 109

Agile 2016 2017 2018 109

Gunther Verheyen

DECEMBER 19, 2018

In 2013 I accidentally created a book, “Scrum – A Pocket Guide” In 2018 I deliberately evolved my Scrum travel companion into a second edition. I equally enjoyed updating my book to a second edition 5 years later. Certainly as my book remained in the best-seller list of my publisher all the time?

SCRUM 77

SCRUM 2013 2016 2017 77

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 2128, International Technical Paper , 2016. Project Risk Management: Lessons Learned from Software Development Environment,” Y. 255, April 2010. 920, November 2004.

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. 2128, International Technical Paper , 2016.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Digite

MAY 15, 2018

It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. People on software development teams, regardless of Scrum or Kanban, will goal set, seek feedback, deliver increments of product, and reflect on how they work.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Herding Cats

APRIL 4, 2019

So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. I'm not expecting anyone to read all these books. All these books are in print. Verlag, 2016. No References? Then it's likely just an anecdotal opinion.

Risk Management 43

Risk Management Risk 2003 2011 43

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. Gano, Atlas Books, 2007. Hooey, Safety Science, Volume 85, June 2016, Pages 241–257.

2014 45

2014 Aerospace 2011 2013 45

LiquidPlanner

NOVEMBER 2, 2017

We’ve broken this list into five sections: Books. While there are a lot of books out there about the proper ways to deliver bad news, this one is directed at project managers. This book helps build a foundation, walking through the essentials of people and project management. Massive Online Open Courses (aka MOOCs).

Technical Review 113

Technical Review 2018 Underperforming Technical Team Certification 113

International Institute for Learning

SEPTEMBER 20, 2022

Martine Haas and Mark Mortensen, “The Secrets of Great Teamwork”, Harvard Business Review, June 2016. Beedle, “Agile Software Development with Scrum”, Upper Saddle River, NJ, Prentice-Hall, 2002. Ashley Bell, “14 Essential Team Management Skills for First-Time Managers” , snacknation.com, 2022. Schwaber, K. Hackman, J.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

International Institute for Learning

JUNE 22, 2022

Kanban is a flow-based management practice initially developed to reduce inventory and manufacturing costs. These practices are now widely used to visualize and manage work in industries as diverse as software development, operations support, and non-profit management. Founding Principal. Project Management Essentials.

Technical Review 52

Technical Review Software Review Lean PMI 52

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. Agile Software Development. Presentations and Briefings.

2003 54

2003 2011 2008 Performance Measurement 54

Rebel’s Guide to PM

SEPTEMBER 26, 2016

About the Authors: Elizabeth Harrin ( you know me ) is the author of several project management books, including Collaboration Tools for Project Managers (PMI, 2016). She writes the blog GirlsGuidetoPM.com and regularly reviews emerging software tools online. She graduated in Mathematics and with an MBA in Global Management.

Software Review 150

Software Review Software Technical Review PMI 150

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L.

2003 46

2003 2014 2015 2011 46

Stepping Into Project Management

AUGUST 6, 2018

The book has been recently published in Amazon and if you have heard of Agile, work as part of Agile teams or would like to have a better understanding how to make it across countries to work as one team- the challenges and the tools that will help you bribe the gap, this book is for you. That’s how we decided to write a book.

Agile 40

Agile Leadership 2016 Influencer 40

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Architecture (#Architecture).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

OCTOBER 16, 2018

The book that contains that paper and provides the specific approach to modeling the future is Statistics for Experimenters: An Introduction to Design, Data Analysis, and Model Building , Georg E. You can get this book on Amazon for $10.00, read it and confirm that the opening conjecture is a fallacy. "The Box, Willaim G.

Aerospace 41

Aerospace Engineering 2012 2014 41

Planio

DECEMBER 4, 2019

And just because you know the steps of the software development lifecycle or how to write a statement of work doesn’t mean you can successfully manage a project. A 2016 Harvard Business Review article found that 69% of managers say they’re uncomfortable communicating with employees. Unfortunately, this isn’t always easy.

Underperforming Technical Team 176

Underperforming Technical Team 2019 Software Review Technical Review 176

MPUG

MAY 6, 2021

High-level software design will all be done in the traditional waterfall then they will spin into an agile environment to do the software development part of it, then they’ll spin back out of Agile to go back and do something like user acceptance testing. Normally, they’ll do requirements gathering, system design.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Paymo App

JANUARY 19, 2018

At the same time, you should know that many project managers have had previous other jobs such as software developers, marketing managers, accountants, designers, and so on. The main study resource is the book “Managing Successful Projects with PRINCE2”. Scrum is used predominantly in software development projects.

2018 111

2018 Prince2 Certification Technical Review 111

PM Basics

OCTOBER 26, 2020

In addition, you can get a simple template I developed and used throughout 10 years as a software development project manager. The objective of this project is to develop a site with the speed performance level stated in the requirements. Release date: Due no later than October 20, 2016. Summary budget: $100,000.

Software Review 52

Software Review Underperforming Technical Team Risk Management Project Life Cycle 52

MPUG

OCTOBER 9, 2019

As the president and founder of Advisicon, Tim has also written over 38 books on PM methodologies and technologies. And so this is where agile kind of fits in and isn’t just necessarily only for software development. But it is clearly not limited to just software. Now, this is pretty new.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

MPUG

NOVEMBER 14, 2019

His latest contributions being the latest version of the Microsoft Project Do’s and Don’ts book, which is available now on Amazon. However, all the reports except for the Agile reports, are also part of the 2013, 2016, and 2019 versions of Microsoft Project. So welcome back, Erik. So let’s click on close.

2013 40

2013 Finance 2007 Software Review 40