Agilemania

FEBRUARY 22, 2021

Software Development. The Sprint Review is a working session, and the Scrum Team should avoid limiting it to a presentation. Kanban vs. Scrum- Cadence . The lead time defines the time between the arrival of a new task and its departure. Here are the Major Differences Between Scrum and Kanban. Lean Manufacturing.

SCRUM 52

SCRUM Lean Software Review Cadence 52

Herding Cats

APRIL 8, 2017

The notion that innovation and engineering - software engineering - are somehow in conflict is common. . The ideas must be movel - different from what's been done before - but they can't be simpmply bizarre; they must be appropriate to the problem or opportuntiy presented. Two Books in the Spectrum of Software Development.

Web Development 37

Web Development Software Engineering Engineering 2010 37

Leading Agile

JUNE 5, 2018

” For instance, they would fully define the database schema before starting any other work. This could be the only Story the team tackles in their first development cadence or iteration or Sprint or what-have-you. An API is a defined way for programs to interact with other programs. Untracked files: (use "git add."

Controlling 67

Controlling Initiating Cadence Defining 67

Planio

APRIL 24, 2023

According to the Association for Project Management : “Project management is the application of processes, methods, skills, knowledge, and experience to achieve specific objectives, according to defined acceptance criteria, within agreed parameters.” Find the right meeting cadence for you and your team.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Leading Agile

AUGUST 19, 2020

The good news is that many aspects of Transformation are definable and repeatable, so they can be predictable. Product owners not quite present or the product owners delegated to a BA. In my organization, LeadingAgile, I have a software development team, I have zero need for predictability, like zero need for predictability.

Agile 100

Agile SCRUM Governance Government 100

Planio

MAY 9, 2022

When Google decided to research what quality defines the most successful teams, they ended up with an unexpected answer: psychological safety. It’s not the same as implementing a new software development process or following a checklist when you finish a project. Set ground rules for how teams interact. That’s the only way.

Underperforming Technical Team 147

Underperforming Technical Team Innovation Cadence Risk Management 147

Wrike

FEBRUARY 20, 2023

It is especially useful in software development and enterprise product management as these teams tackle projects and programs on extended timelines with continuous improvements, upgrades, and iterations released and delivered to customers over time. Each level presents a different perspective and focus.

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

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. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Workamajig

JANUARY 11, 2021

Actual Time Expended: The actual time spent on an activity from the Actual Start to the present date. Benefits Framework: This defines the expected benefits of the project, the specific operations it would affect, and how the project's performance would be; a) realized, and b) measured. In most projects, this unit is 'hour'.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Leading Agile

FEBRUARY 11, 2019

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

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

OCTOBER 16, 2019

If you have any questions during today’s presentation please send those over at any time using the chat question box on the go to webinar control panel. You’re going to see this coming out at a very fast cadence. We do plan to answer those for you as time permits at the end of the session today.

Agile 40

Agile Technical Review Software Review Engineering 40

MPUG

JUNE 1, 2022

Melanie: Jeff is currently the Training and Development Manager for Edwards Performance Solutions. As such, he oversees the production and maintenance of courses on project management, systems engineering, software development, business process improvement, and cyber security. I’ll hand the presentation over to you.

PMI 59

PMI Software Review Estimate Risk Management 59

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Are stakeholders involved in defining the examples? I often hear people say they can’t afford to create consistently-defined environments throughout the pipeline. But what are they scripting?

Software Review 78

Software Review Software Technical Review Development Team Review 78