Scrum.org

NOVEMBER 12, 2018

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team. Meetings can be included.

SCRUM 154

SCRUM Development Team Review Estimate Software Review 154

Scrum.org

NOVEMBER 7, 2018

SAFe's approach to product ownership is that scale is achieved by splitting the product ownership role between Product Management, which is more like the classic Scrum Product Owner, and the Product Owner, which is indeed more like a proxy or technical product owner working more closely with teams.

SCRUM 138

SCRUM Development Team Review Technical Review Cadence 138

Scrum.org

OCTOBER 2, 2018

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. The Increment Got Us Here.

Cadence 134

Cadence Development Team Review Software Review Technical Review 134

Scrum.org

OCTOBER 2, 2018

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. The Sprint Increment Got Us Here.

Cadence 128

Cadence Development Team Review Software Review Technical Review 128

Scrum.org

MAY 7, 2019

One of the responsibilities of a Scrum Master is to coach the Development Team in self-organization. Therefore, it’s up to the Development Team to determine the best way to accomplish its work and build ‘Done’ Increments. Sprint Review. But there’s no working software at the end of the Sprint. Presentation

SCRUM 185

SCRUM Development Team Review Leadership 2018 185

Scrum.org

NOVEMBER 7, 2018

SAFe's approach to product ownership is that scale is achieved by splitting the product ownership role between Product Management, which is more like the classic Scrum Product Owner, and the Product Owner, which is indeed more like a proxy or technical product owner working more closely with teams.

SCRUM 114

SCRUM Development Team Review Technical Review Cadence 114

Scrum.org

JUNE 14, 2019

This could be complexity related to software development, product development or something else in which there is more unknown than known. Based on the different scenario’s, the Product Owner could set Sprint Goals, update the product roadmap, engage with stakeholders and offer clarity to the Development Team.

Development Team Review 113

Development Team Review Defining SCRUM Software Review 113

Scrum.org

FEBRUARY 25, 2024

Scrum Anti-Patterns GPT’s Answer Organizational issues often lead to Scrum anti-patterns that can hinder the effectiveness and efficiency of Scrum Teams. Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams​​.

SCRUM 189

SCRUM ChatGPT Technical Review Development Team Review 189

International Institute for Learning

JUNE 22, 2022

Transforming organizations to become Lean and Agile while maintaining high levels of performance within its teams requires a strong focus on people. After all, these high-performing teams are the ones that deliver change and growth. My role model for personal development and lifelong learning is my grandfather Gustav.

Telecoms 52

Telecoms 2022 Lean Development Team Review 52

Scrum.org

FEBRUARY 21, 2023

Additionally, I have a strong background in product discovery, which involves identifying customer needs, validating product ideas, and conducting experiments to inform product development decisions. Background : As the “Manifesto for Agile Software Development” states, it is mainly about adaptability over following a plan.

ChatGPT 161

ChatGPT Development Team Review Technical Review SCRUM 161

Scrum.org

NOVEMBER 14, 2019

It came to a head when there was no time for Lucy to code anymore. It was a struggle to figure out what makes me a good manager and how you measure your success; it used to be palpable when I was a developer - I delivered this code to production.". "It Lucy missed coding. Now we were closing stories early on.

Software Review 21

Software Review Technical Review Development Team Review SCRUM 21

Teamweek

MARCH 6, 2024

According to research, 81% of managers in tech say that upskilling programs are highly effective in preparing their teams for new projects. Upskilling helps employees and companies close skills gaps and gives businesses a competitive advantage. Earn a certificate Want to close some knowledge gaps and improve your career path?

CTO Hire 52

CTO Hire Technical Review Fractional CTO Development Team Review 52

Scrum.org

JUNE 18, 2021

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 186

2010 SCRUM 2006 Software Review 186

Scrum.org

MAY 5, 2020

Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and Development Team. How does working remotely impact the collaboration with the Development Team? For example, the Daily Scrum is attended by the Development Team only.

SCRUM 183

SCRUM Development Team Review Technical Review Consulting 183

Scrum.org

APRIL 7, 2022

Team cognition is similar in the sense that the entire team can be thought of as a body, where each member (the limbs) has to learn how to coordinate their work effectively to move forward. This shared understanding is captured in the “team mental models” that drive team cognition. It takes time to develop teams.

Underperforming Technical Team 175

Underperforming Technical Team 2007 2006 2009 175

Scrum.org

APRIL 11, 2019

I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. The Product Owner should develop an inspiring vision and a plan to make it happen. Component ownership.

Underperforming Technical Team 145

Underperforming Technical Team SCRUM Development Team Review Software Review 145

Scrum.org

OCTOBER 19, 2020

Daily Scrums are an important part of Scrum, but not all Daily Scrums need to be formal — a Development Team should not have a Daily Scrum for the sake of having it; it serves a different purpose than ticking off a box on a checklist. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum.

SCRUM 166

SCRUM Underperforming Technical Team Software Review Development Team Review 166

Scrum.org

FEBRUARY 8, 2020

The business people would point out that the IT people were not able to deliver quality code. I had various conversations and workshops with the development teams and the leadership. It was no surprise that team ownership decreased over time and ‘POCLAC’ activities increased a lot. Output driven development.

Underperforming Technical Team 159

Underperforming Technical Team Software Review SCRUM Technical Review 159

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

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

Teamweek

AUGUST 7, 2023

Recruiting developers in today’s job market can be as easy as knitting a sweater with spaghetti. ? With software development being the world’s most in-demand profession in 2023, tech companies and every technical recruiter on planet Earth are vying for their attention. What does a developer do?

Technical Review 52

Technical Review CTO Hire Software Review Software Engineering 52

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. This is a closed loop system optimization process applied to all the projects we work.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Scrum.org

MARCH 19, 2023

Here are some of the key differences between the two versions: Focus on the Scrum team : The Scrum Guide 2020 places more emphasis on the Scrum team, rather than just the Development Team. The Product Owner and Scrum Master are now considered equal members of the Scrum Team.

ChatGPT 155

ChatGPT SCRUM Technical Review 2020 155

Scrum.org

FEBRUARY 10, 2022

Bitte beachten Sie, dass ich Grammarly verwendet habe, um Tippfehler und Zeichensetzung zu korrigieren: While the cross-team big room planning is very useful, in my experience, SAFe is top-down. I would be in favor of a scaled framework that empowers teams to solve customer problems the way that Scrum does.

Lean 186

Lean Software Review 2022 Technical Review 186

Scrum.org

FEBRUARY 7, 2022

Please note that I used Grammarly to correct typos and punctuation: While the cross-team big room planning is very useful, in my experience, SAFe is top-down. Executives that are not close to the customer problems make the decisions at the portfolio level, and teams execute, which can lead to disengaged teams.

Lean 154

Lean Software Review 2022 Technical Review 154

MPUG

OCTOBER 22, 2020

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. Today’s session is eligible for one PMI PDU in the technical category, and the MPUG, the activity code for claiming that is on the screen now.

Technical Review 40

Technical Review Software Review Governance Government 40