Herding Cats

MAY 10, 2019

Risk Management is essential for development and production programs. 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. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Sudipta Lahiri

AUGUST 1, 2014

Yet, without putting into place a strong foundation, any expectation of sustained profit is misplaced. Shitsuke: Develop the habit of abiding by what is laid down. It is important to recognize that while the Top 3S help to get better using Kaizen, the Bottom 2S help us to sustain the gains from the Top 3 ! Lesson III: 3S vs 2S.

Software Review 20

Software Review Underperforming Technical Team Technical Review Lean 20

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. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Resource Guru

SEPTEMBER 6, 2023

How do you bring in more clients to keep growing sustainably? Agency growth is the process of expanding your agency’s operations and capabilities by growing its client base, enhancing its service offerings, and strengthening its team to meet demand. A gency growth is about managing lots of moving parts—and managing them well.

Technical Review 52

Technical Review Underperforming Technical Team Sustainability Software Review 52

Leading Agile

APRIL 15, 2019

Similarly, a team should complete the work item or ticket or story (or whatever they call it) they’re working on before picking up the next one. Many software developers will tell you it takes between 10 and 20 minutes to get back into the zone, depending on the task.

Software Review 117

Software Review Underperforming Technical Team Lean Technical Review 117

Leading Agile

FEBRUARY 11, 2019

Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. How can the same principle be a good idea in 2002 and a bad idea in 2019? It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.”

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

Leading Agile

JANUARY 28, 2019

I’m not suggesting this degree of simplification is automatically or always a Bad Thing. It can become a Bad Thing when we lose sight of the larger context of our work. Software testers. Software developers/maintainers. It only becomes a Bad Thing when you assume you’ve finished. Only One Metric?

Agile 107

Agile Underperforming Technical Team Development Team Review Engineering 107

Herding Cats

APRIL 16, 2019

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. Chartering the Team , Chartering empowers team members, both individuals and collectively. Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. Now it’s not to say that processes and tools are bad or documentation is bad or putting something in writing, but the idea is that there’s an investment that really will be a little bit different.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40