article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Ready to transform your approach to project management and software development? Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Columns include "Reported," "Confirmed," "In Development," "Testing," and "Deployed."

article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

This ties closely into research on team cognition and cross-functionality. We know from research in teams that even light conflict has a negative effect on team productivity (De Dreu & Weingart, 2003). Closing words. Analysis of fault generation caused by stress during software development. Furuyama, T.,

2004 230
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

This corresponds with research on autonomous teams, as well as principles of Agile software development. If organizations are unable to develop high-performing teams from mostly stable teams, it is very unlikely they will succeed with more fluid team designs. “ Closing Words. So … stable teams or fluid teams? References.

article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Nine Best Practices of Project Management , Software Program Managers Network (SPMN). Open Loop / Closed Loop Project Controls. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Agile Software Development. Project Governance.

2003 54
article thumbnail

The Classic Misunderstanding between Principles, Practices, and Process

Herding Cats

SAs an early user (as a FORTRAN 77 developer on Software Intensive System of Systems for Ballistic Missle Defense systems), the principles of Iterative and incremental development, emergent requirements, customer in the loop , and other principles, practices, and processes found in Agile started long before the Agile Manifesto.

2003 56
article thumbnail

Can We Still be Agile?

Leading Answers

We should also remember when the agile principles were developed in 2001, video conferencing was not as straightforward or familiar as it is today. It was not until 2003 that Skype and other applications provided widely used and low-cost options for getting some face time. First, Type-1 teams are fully collocated.

Agile 145
article thumbnail

Risk Management is How Adults Manage Projects

Herding Cats

It just closed the loop faster. 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. Oriented Perspective , 1st Edition, Terje Aven, John Wiley & Sons, 2003. This is good, but it doesn't reduce risk.