Leading Agile

JULY 18, 2023

Third, how are we reproducing working tests in software? When people make such statements, they usually mean that they have trained product owners and a proficient Scrum master, and their team consistently follows the cadence of sprint planning, daily stand-ups, interviews, and retrospectives. First, how are we forming teams?

Agile 105

Agile Software Review Certification Technical Review 105

Leading Agile

APRIL 24, 2019

Business agility is what organizations are looking for; agile software development may be one enabling factor in achieving it, but it isn’t the point of a transformation. Dividing your transformation initiative along the seams of the technical infrastructure will often be a suboptimal approach. Half-Agile Transformations.

Technical Review 115

Technical Review Agile Infrastructure Cadence 115

The Strategic Project Manager

NOVEMBER 7, 2022

To provide an initial taste of agile methods, consider the following list: Scrum – Scrum codifies the ‘pillars and values’ of transparency, inspection, and adaptation. The sprint cycle includes key ‘ceremonies’: sprint planning, daily scrum, sprint review, and sprint retrospective.

Agile 52

Agile Software Review Cadence SCRUM 52

Rebel’s Guide to PM

AUGUST 6, 2022

It’s fine to have a different cadence at different points in the project lifecycle. If you are expecting the project oversight committee to make a decision at the meeting, make sure that they have information in advance of your meeting so that they can review the different options. Action review and next steps. Key decisions.

Governance 369

Governance Government Risk Management Technical Review 369

Agilemania

DECEMBER 2, 2021

SAFe endorses alignment, transparency, collaboration, and product delivery involving large size teams.The core of SAFe is based on four bodies of knowledge which are agile software development, lean product development, systems thinking, and DevOps. Apply cadence and synchronize with cross-domain planning. Take an economic view.

Technical Review 98

Technical Review Agile Software Review Lean 98

Agilemania

DECEMBER 13, 2021

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Code Quality. Apply cadence and synchronize with cross-domain planning. In the Scaled Agile Framework, every team member works diligently. Architecture and Design Quality.

Agile 98

Agile Lean Software Review Technical Review 98

Scrum.org

FEBRUARY 22, 2021

To prevail in today’s game of an accelerated innovation-based competition—software is eating the world—, every organization needs to acquire a holistic understanding of an agile product creation process: A vision leads to a strategy that (probably) results in a portfolio of products (and services). Then we don’t have those questions anymore.”

Software Review 146

Software Review Technical Review Cadence SCRUM 146

Scrum.org

NOVEMBER 16, 2018

Is it software based or do users use physical boards? My clients get to decide the cadence of our “events.” Most clients prefer the weekly check-in that closely resembles a combination of a Sprint Review and Retrospective. Our cadence isn’t set to a specific time box but rather by sets of 5 Skills, Habits, and Behaviors.

SCRUM 125

SCRUM Cadence 2018 Agile 125

Planio

AUGUST 9, 2021

What is the best project scheduling software to use? For example, maybe you need to finish cleaning out old code or squash some lingering bugs before building out new features. Ask each person to help estimate their workload, uncover dependencies, and set deadlines for due dates. How do Agile teams create a project schedule?

Software Review 78

Software Review Technical Review Estimate Agile 78

Planio

JULY 4, 2022

Sprint review ceremony. Agile ceremonies — also known as Scrum ceremonies or just ‘events’ — are specific events that provide a structured framework for iterative software development processes. Agile is an umbrella term for different iterative and feedback-driven software development processes. (And why do they matter?).

Agile 88

Agile Technical Review Development Team Review Software Review 88

Agilemania

MARCH 19, 2021

Software Development. Sprint Review. And through safe to fail experiments, they should take improvement initiatives. All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. Kanban vs. Scrum- Cadence . Daily Scrum.

SCRUM 98

SCRUM Lean Software Review Cadence 98

The Strategic Project Manager

JUNE 28, 2022

Project vision – At initiation of the project, there is a vision for what the project is to accomplish and produce. Sprint Review – This entails testing the sub-products developed, demonstrating completion to the team and customer, and adjusting the backlog based on the outcome of the sprint. Sprints and the Team.

Process 40

Process SCRUM Agile Cadence 40

Digite

MARCH 1, 2017

However, I had not seen Kanban being applied to software development, project management, etc. I guess that was my initial foray into a “proto-kanban” implementation – I was still learning! I got to understand much better the application and benefits of the Kanban method for software Development and knowledge work. Our Cadences.

Software Review 60

Software Review Lean Cadence Engineering 60

Leading Agile

AUGUST 13, 2018

Technical teams who are building or supporting application software usually work from a prioritized list of improvements, new features, and ideas to try out. People leave and are replaced with new team members who don’t know the code base or the organization’s internal procedures. Scrum calls the list the Product Backlog.)

Software Review 78

Software Review Technical Review Cadence SCRUM 78

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. What is the business context? Support, SLAs, Meeting Market Requirements. This is a loss to the company.

Underperforming Technical Team 71

Underperforming Technical Team Software Review Cadence Software 71

Digite

MARCH 2, 2018

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established. What is the business context? Support, SLAs, Meeting Market Requirements. This is a loss to the company.

Software Review 66

Software Review Underperforming Technical Team Cadence Software 66

Agilemania

FEBRUARY 22, 2021

Software Development. Sprint Review. And through safe to fail experiments, they should take improvement initiatives. All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. Kanban vs. Scrum- Cadence . Daily Scrum.

SCRUM 52

SCRUM Lean Software Review Cadence 52

Wrike

DECEMBER 20, 2021

Alongside that, full-time employees are increasingly working as members of dispersed, global teams, communicating and coordinating via online software and apps. Over the years, however, its scope has broadened to encompass a wide range of activities and initiatives. For instance, it allows employees to work from anywhere in the world.

2022 41

2022 Artificial Inteligence Technical Review Cadence 41

Leading Agile

AUGUST 19, 2020

So the first lens or the first set of foundational things that we’re going to talk about when it comes to predictability is the idea of the three things, teams, backlogs, working tested software. They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right?

Agile 89

Agile SCRUM Governance Government 89

Scrum.org

JULY 31, 2023

To realize this ambition, a transformation was initiated that aimed at implementing a uniform agile way of working with independent, integrally responsible customer journey teams. They did not have the skills or authorization to make software and configuration changes in the banking systems.

Technical Review 158

Technical Review Software Review 2022 2021 158

Leading Agile

JANUARY 21, 2021

So it’s like the ability to form teams, the ability to create clear backlogs the ability to get to a working tested increment of software at the end of every sprint. So again, I’m anchoring not on feature level agility that we often talk about when it comes like agile software development but how do I pivot an organization?

Sustainability 83

Sustainability Agile SCRUM Technical Review 83

Leading Agile

APRIL 7, 2023

That having weekly planning cadences; daily standups, reviews, and retrospectives would give people a reason to get in the same room and collaborate. Things really take off with the advent of the CSM certification and PMI finally recognizing Agile as a legitimate way to do software project management. The governance model?

Agile 133

Agile Governance Government Underperforming Technical Team 133

Planio

APRIL 24, 2023

Updating project management software to keep their team on track 9. But over the years, project managers have learned to follow a strict project lifecycle, which helps them manage every step of the journey, from establishing initial goals to handover and closing. Creating actionable project plans 5.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Leading Agile

MAY 3, 2023

The roles, the ceremonies, the artifacts, the cadences, all those different things that we model as implementation details. Are we doing reviews? What kind of reviews and retrospectives are we doing and how are we doing them?” It happened with RUP, it happens with SAFe, it happens with Scrum, it happens with everything.

Agile 62

Agile Technical Review Governance Government 62

Scrum.org

APRIL 11, 2019

Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. Connect the dots by making reporting on market research data and customer feedback data a mandatory item of the Sprint Review.

Underperforming Technical Team 146

Underperforming Technical Team SCRUM Development Team Review Software Review 146

Leading Agile

MARCH 31, 2020

You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. So, also about the time that you and I met you were doing some work with PMI and the OPM three initiative? And that was about the time that I was starting to develop the teams backlogs, working testing software.

Agile 63

Agile Technical Review SCRUM Engineering 63

Leading Agile

APRIL 4, 2023

The Scaled Agile Framework wasn’t exactly what the authors of the Agile Manifesto imagined 20 years ago when they set out to define a better way of building software. It requires the ability to continuously deploy software, to continuously get feedback on it. We do reviews and retrospectives, right? That’s typically Scrum.

Technical Review 87

Technical Review Agile SCRUM Governance 87

Redbooth

APRIL 26, 2018

The model has been favored by software engineers for its efficacy and flexibility, and it’s beginning to catch on in agencies and startups. Cut down work periods through sprints, daily standups, and reviews. Initially, this may seem like a lot of contact. Reviews : Feedback sessions held at critical junctures.

Agile 128

Agile Technical Review Software Review Cadence 128

Workamajig

JANUARY 11, 2021

Activity ID: An alphanumeric code used to identify an activity. The agile approach is usually used in software projects where the scope is not always known and adaptability is prioritized. Projects might additional calendars as well to show resource availability, communication cadence, etc.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. This could include goal-setting exercises or meeting cadence.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Leading Agile

JUNE 29, 2023

Executives aren’t solely focused on delivering software to customers. I once worked with a large agriculture company that aimed to implement a software solution for their tractors in March. I explained that the desired outcome was scientifically impossible to achieve before March due to the intricate technical requirements.

Agile 77

Agile Technical Review Executing Influencer 77

Scrum.org

AUGUST 9, 2022

Business does not understand the complexity of software development or engineering work. Just initiate. initiative comes from your employees, support them by actions. I found it useful when I initiate the conversation, trying simultaneously to empathize and understand. Remember about cadences. Sprint Reviews.

Technical Review 179

Technical Review Cadence 2005 Initiating 179

Leading Agile

FEBRUARY 11, 2019

It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” The overhead of repeated team-forming affected delivery schedules by introducing delay into every initiative. How can the same principle be a good idea in 2002 and a bad idea in 2019? What has changed?

Agile 94

Agile Underperforming Technical Team Software Review Technical Review 94

MPUG

OCTOBER 16, 2019

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. And today’s session is eligible for one PMI PDU in the technical category, and the code for claim that is on the screen now, that’s mpugwebnlearn091819.

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

OCTOBER 3, 2023

And so we ended up with a lot of folks doing standups and sprint planning and story cards and sticky notes and burndown charts and reviews and retrospectives. And so I was thinking about Scrum and so I just lifted this off of Mike Cone’s website and it’s attributed, so I hope he doesn’t mind too much mountain good software.

Governance 62

Governance Government SCRUM Agile 62

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). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Teamweek

AUGUST 29, 2023

Including clear ‘Apply now’ buttons or even a nifty QR code makes the candidate experience more streamlined, and less likely that qualified candidates drop the application process. Drive applications to your career page in a fun, engaging way, like with a QR code. Source What works well Doing things differently.

Software Review 52

Software Review Technical Review Cadence Influencer 52