Leading Agile

APRIL 24, 2019

Tech Infrastructure != Many organizations divide their technology stack between front-end and back-end systems and place an API boundary between the two. I’m including all IT resources “in front of” the API layer in the organization’s technical infrastructure. Value Stream. Half-Agile Transformations.

Technical Review 115

Technical Review Agile Infrastructure Cadence 115

Scrum.org

MARCH 11, 2024

Join Stefan in one of his upcoming Professional Scrum training classes ! Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. Technically, it is the prerogative of the Product Owner to cancel Sprints.

Technical Review 153

Technical Review Underperforming Technical Team Software Review SCRUM 153

Scrum.org

DECEMBER 7, 2023

For example, Scrum includes five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and the Sprint Retrospective. PI Planning serves as the cornerstone of the Agile Release Train within SAFe, establishing a synchronized cadence for multiple teams to work together towards a common goal. It is deliberately incomplete.

SCRUM 158

SCRUM Software Review Agile Software 158

Scrum.org

NOVEMBER 7, 2018

In SAFe's Program Level, a key piece is the Agile Release Train which is considered a team of Agile teams. SAFe's creators seem to enjoy the fact that it is complicated since it provides an excuse for more and more training possibilities. SAFe has a cadence at the Team and Program levels. Well, let's unpack this.

SCRUM 110

SCRUM Development Team Review Technical Review Cadence 110

Inloox

JULY 1, 2021

Large corporations in particular, which are in urgent need of more agility due to entrenched structures, usually have the hardest time implementing an agile transformation. Team and technical agility: Agile teams are the cornerstone of business agility. But it’s not that easy. How do you build the framework for holistic agility?

Technical Review 100

Technical Review Lean 2011 Cadence 100

Agilemania

DECEMBER 2, 2021

Apply cadence and synchronize with cross-domain planning. Program Increment (PI) planning is a meeting of numerous teams that are a part of an Agile Release Train (ART) where they gather to plan the roadmap, work on features and additions, and recognize cross-team reliance. Build Incrementally with quicker integrated cycles.

Technical Review 98

Technical Review Agile Software Review Lean 98

MPUG

SEPTEMBER 4, 2023

What agile adds to this, therefore, is a distinct cadence of its own iterations or drawdowns of tasks into the Work in Progress part of the Kanban Board. Rapid changes in the market demand arising from social trends, competitor activities, or technical capability, for example. Rapid development in the technology available.

Risk Management 98

Risk Management Risk Agile Technical Review 98

MPUG

MARCH 8, 2021

It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. When you fire a gun in the dark, it’s difficult to aim due to the lack of light. Developers, with all due respect to them, are generally optimistic people.

Lean 65

Lean Software Review Technical Review Agile 65

Scrum.org

JANUARY 4, 2022

It is a container event, which means that it contains all other events, including Sprint Planning, the Daily Scrum, the Sprint Retrospective, and the Sprint Review. The duration of the Sprint is timeboxed to a maximum of one month, establishing a cadence within which the Scrum team works together to deliver value.

SCRUM 179

SCRUM 2020 Cadence Technical Review 179

Scrum.org

MAY 14, 2020

Technology alone won’t solve the problem. How should we collaborate to review the outcome of our work? How can we find the right cadence for collaboration and when should we collaborate? In our consulting work we frequently train, mentor and coach our clients to use Scrum as a management framework. Roll out Zoom?

Agile 164

Agile Technical Review Software Review Cadence 164

Digite

AUGUST 21, 2017

In 2015, in a blog post called Kanban Cadences , David Anderson laid out a set of 7 Kanban cadences or meetings that provide comprehensive opportunities for feedback, planning, and review in an enterprise. In my experience, 3 of these are critical for ensuring that a Kanban initiative gets off the ground successfully.

Development Team Review 151

Development Team Review Cadence Technical Review 2015 151

Scrum.org

MAY 27, 2021

We’ve already discussed the importance of decentralised command and decision-making in an earlier blog, outlining how managers need to be able to train, mentor and teach their teams. 4 – The Review. In this way, the Review makes transparent what was delivered, sharing successes and answering any questions.

Agile 248

Agile Cadence Technical Review Software Review 248

Scrum.org

DECEMBER 7, 2020

The Product Owner theses also address the Product Owner’s part in Scrum events from Sprint Planning to Sprint Review to Sprint Retrospective, and the Daily Scrum. While the product roadmap addresses strategic aspects of product planning, the Product Backlog addresses tactical and technical development issues. The Product Owner Theses.

Technical Review 205

Technical Review SCRUM 2020 Estimate 205

Rebel’s Guide to PM

AUGUST 6, 2022

It’s fine to have a different cadence at different points in the project lifecycle. For example, hold the meeting the week before you need approval to send out training material, or similar, so that the right people can make the decision there and then. Action review and next steps. When to hold the meetings. Key decisions.

Governance 363

Governance Government Risk Management Technical Review 363

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. You train your teams on Agile, the teams start using Agile, recognize their impediments, and change the systems to be more effective at delivery. The technology architecture?

Agile 133

Agile Governance Government Underperforming Technical Team 133

Velociteach

FEBRUARY 1, 2023

Projects using well-understood solutions and technologies require less rigor. Problem complexity, technical complexity, compliance requirements, and the cost of change factor into this decision. Projects where the problem and technical complexity are low, and the cost of change is high may favor a predictive methodology.

Planning 52

Planning Technical Review Governance Government 52

Agilemania

DECEMBER 13, 2021

Apply cadence and synchronize with cross-domain planning. Recognize value streams and Agile Release Trains (ARTs). Train teams and flag the ART. It provides a secure and reliable method for highlighting, performance, and delivery through Agile Release Trains. Build Incrementally with quicker integrated cycles.

Agile 98

Agile Lean Software Review Technical Review 98

Kiron Bondale

AUGUST 6, 2017

For example, technology deliverables might be completed in an agile manner whereas change management deliverables such as training collateral get produced in a traditional manner. In others, deliverables themselves are produced in a hybrid manner.

Agile 136

Agile Cadence Technical Review Influencer 136

MPUG

FEBRUARY 1, 2021

As per PMI, there are three types of PMOs: A supportive PMO largely plays a consultative role such as providing templates, imparting training and coaching, and storing lessons learned across projects. Training: Facilitating or conducting, providing coaching, and mentoring. Training, Coaching, and Mentoring. Types of PMOs.

Agile 94

Agile PMO Technical Review Cadence 94

Leading Agile

JULY 18, 2023

If not, then we start measuring things like people trained, teams doing Scrum, or the organization’s sentiment toward Agile to tell us if we’re succeeding. Creating an Agile Culture vs Achieving Business Benefits So sometimes people will tell me things like, Yeah, we’re doing Scrum really well, daily standards, reviews, retrospectives.

Agile 105

Agile Software Review Certification Technical Review 105

Leading Answers

MARCH 7, 2019

When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable. The development team wants interesting work using new technology and skills to further their craft.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Scrum.org

MARCH 28, 2022

Join Stefan in one of his upcoming Professional Scrum training classes ! All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. Hence you may notice tickets queueing in the code-review-column, for example.

SCRUM 151

SCRUM Technical Review Software Review Consulting 151

Teamweek

JULY 27, 2023

This is followed by creating an action plan, setting a timeline, planning regular reviews, and documenting the plan. Progress Review Regular review dates to assess progress and make necessary adjustments. Review progress with the manager every quarter. What is a professional development plan?

Planning 52

Planning Technical Review Leadership Cadence 52

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. If technology can pass a Wharton MBA exam , maybe, it deserves some attention. Professional Scrum Master Training w/ PSM I Certificate — Live Virtual Class: February 7-10, 2023.

ChatGPT 177

ChatGPT Agile Artificial Inteligence Consulting 177

Leading Agile

MARCH 31, 2021

One common pitfall is assuming that the technological encapsulation of products by breaking dependencies (through a loosely coupled architecture and a mature CI/CD pipeline) is a prerequisite for the encapsulation of value streams. While the mechanisms of these antipatterns are slightly different, they all end up driving the same impact.

Underperforming Technical Team 118

Underperforming Technical Team Software Review Technical Review Governance 118

Planio

AUGUST 1, 2022

According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. Bring in ongoing training. Technology: Agile organizations need to trust their data and have the infrastructure ready to build and test new ideas rapidly.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Strategy Execution | PMO Perspectives

SEPTEMBER 5, 2019

Even though organisations are executing more projects to get more work done, they are also managing bigger and increasingly transformational projects due to the increasingly volatile, uncertain, complex and ambiguous (VUCA) business environment. Watch the webinar on how to navigate ambiguity here.

Leadership 65

Leadership Technical Review PMO Cadence 65

Resource Guru

SEPTEMBER 27, 2023

Retainer vs. project-based contracts turnover rates According to Sakas and Company , an agency support and training program, if you’re operating a retainer-oriented agency , a client turnover higher than 20% is a red flag. Be sure to touch base with them regularly , at a cadence that makes sense for both parties.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Transportation 52

Resource Guru

OCTOBER 18, 2023

Non-billable hours: These hours cover internal tasks, like administrative work, training, or non-client meetings. Plan to frontload certain projects, schedule staff training accordingly, or schedule maintenance tasks during those off months. A declining rate could prompt reallocating staff to internal projects or training.

Underperforming Technical Team 52

Underperforming Technical Team Software Review Technical Review Monitoring 52

Project Management Essentials

AUGUST 3, 2019

In my agile training and consulting practice, I have witnessed similar symptoms when an organization is struggling with its agile adoption. Outsourcing is a good option for organizations where technology is not a core or strategic competency. Poorly coded features may be technically complete, but not acceptable.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Leading Agile

MAY 3, 2023

Because if you call us up and you say something like, “Hey, we want some training,” you know, it’s like, “Okay, like what do you want to be trained on? The roles, the ceremonies, the artifacts, the cadences, all those different things that we model as implementation details. Are we doing reviews?

Agile 62

Agile Technical Review Governance Government 62

Wrike

DECEMBER 20, 2021

However, this interaction will require the use of new technology and strategies to manage it properly. Technology plays a huge role in that. If the answer is yes, don’t hold back because of technology complications — the right tech exists to support you. An increased dependency on project management tools.

2022 41

2022 Artificial Inteligence Technical Review Cadence 41

Planio

APRIL 24, 2023

This often involves rounds of training, communications, and some quick fixes/updates as the test team learns more. Then, he works with technical software development experts to estimate the duration of each task and plots it onto a Gantt chart. Find the right meeting cadence for you and your team.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Herding Cats

APRIL 16, 2019

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

FEBRUARY 11, 2019

Because the recovery phase was not officially recognized (typically due to time reporting rules that prohibited honesty regarding overtime), management missed the opportunity to learn from experience and repeated the death march pattern again and again. Stable Team. Projects are assigned to stable, pre-existing teams. Next Steps.

Agile 94

Agile Underperforming Technical Team Software Review Technical Review 94

Project Management Hacks

FEBRUARY 23, 2016

Out of college with a BBA in information technology I started on a help desk providing 2nd and 3rd level support for Cadence, a Silicon Valley software company. I then started managing tech projects while concurrently working on and earning my Master of Science in Information Technology.

Technical Review 53

Technical Review 2015 PMO Information Technology 53

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. All that unplanned activity used to create stress for technical workers. Unexpected or unplanned work isn’t always due to “defects.” There will be stress.

Software Review 79

Software Review Technical Review Cadence SCRUM 79