Scrum.org

FEBRUARY 24, 2019

"The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint." - The Scrum Guide. The Scrum Guide is markedly ambitious in the standard of professionalism it demands of a team. Review Ready. Code Complete.

Development Team Review 191

Development Team Review Underperforming Technical Team Software Review Technical Review 191

Scrum.org

JANUARY 11, 2023

The product owner must have knowledge about the customer needs as well as technical expertise to ensure that the right decisions are made regarding feature selection. They must have knowledge about customer needs and technical expertise to make feature selection decisions. A Day in the Life of a Product Owner.

Technical Review 209

Technical Review Software Review Agile SCRUM 209

Scrum.org

APRIL 28, 2019

In a recent class, while trying to discover new metaphors to convey the true nature of Scrum, it came to my mind the term contextless (that sounds close to the "contactless" credit cards) to describe the mechanical, stringent and simple use of Scrum without considering the needs of the team or organization context.

Technical Review 167

Technical Review SCRUM Software Review Defining 167

Scrum.org

MARCH 2, 2020

Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Scrum Master must prevent them from manifesting themselves: The Scrum Master has a laissez-faire policy as far as access to the Development team is concerned. Forecast imposed: The Sprint forecast is not a team-based decision.

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Scrum.org

NOVEMBER 9, 2020

The following Sprint Planning checklist includes tasks for everyone on the Scrum Team: Preparing the Sprint Planning: T-2 : Address the number of open tickets in the “code review” & “ready for acceptance columns.” Ask the team members to focus on moving tickets to “Done” before starting work on new tickets.

Planning 225

Planning Technical Review Software Review SCRUM 225

Scrum.org

MARCH 18, 2020

On November 22nd, 2019, I gave the closing keynote at Scrum Deutschland, a talk called ‘The Four Things You Do To Prevent Value Delivery.’ Such a study is holistic; it involves looking at the organizational design, technical capabilities, culture and knowledge, and type of control and metrics used to define success. Background.

Technical Review 191

Technical Review Underperforming Technical Team Software Review Development Team Review 191

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 180

Underperforming Technical Team SCRUM Development Team Review Software Review 180

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

SEPTEMBER 10, 2019

The first years of my career as a software developer I worked in a small team of three people where everyone had their specific expertise. I was responsible for the client application we developed for an in-house application. We don't develop software to satisfy our desire for shiny tech stuff - well, not only, at least.

Development Team Review 140

Development Team Review Technical Review Software Review SCRUM 140

Scrum.org

JANUARY 29, 2024

( Japanese version・日本語版 ) When picturing an effective and truly agile product development team, one often imagines a software development team, pushing some software to production every day, maybe multiple times a day, ala Amazon. But not all industries, business models or technologies allow for this to happen.

Agile 208

Agile Technical Review Underperforming Technical Team Development Team Review 208

Scrum.org

NOVEMBER 24, 2021

Intermediary : Acting as an interface between management and the team and the process of disseminating domain knowledge. This includes training, technical support, and preparation for new releases. Which activities can be fulfilled by others in the team, and what is needed for that? technical staff doesn’t need to know”).

2014 233

2014 2008 Technical Review 2019 233

Moira Alexander

JANUARY 12, 2017

Stakeholders and developers closely collaborate on a daily basis. All stakeholders and team members remain motivated for optimal project outcomes, while teams are provided with all the necessary tools and support, and trusted to accomplish project goals. A product or service is delivered with higher frequency.

Software Review 100

Software Review Technical Review Development Team Review Agile 100

Scrum.org

JUNE 22, 2019

I’m simply going to share my perspective as a Scrum Master working closely with developers. That’s not going to be a technical perspective. Although I did try being a developer, I failed miserably… To be clear, whenever I write “developer” in this article, I mean everyone involved in writing software and building products.

Underperforming Technical Team 184

Underperforming Technical Team Technical Review Software Review Development Team Review 184

Scrum.org

FEBRUARY 21, 2023

I am committed to staying up-to-date with the latest industry trends, technologies, and best practices to continuously improve product strategy and drive business outcomes. Finally, I value collaboration and teamwork and believe in creating a supportive environment where the development team can thrive and achieve their best work.

ChatGPT 172

ChatGPT Development Team Review Technical Review SCRUM 172

Planio

JUNE 8, 2022

As products become more complex, technical project managers have quickly become the holy grail for growing businesses. Technical project managers (TPM) bridge the gap between understanding what’s technically possible in a project and managing the resources, timelines, and expectations to get it done. First, learn the basics.

Technical Review 78

Technical Review Software Review Development Team Review Underperforming Technical Team 78

The IIL Blog

JULY 31, 2024

While our tools and techniques might have evolved since 2013, content strategists can find value in looking closely at the basic principles of project management. These steps occur whether the project team uses the traditional waterfall (or phased) project methodology or a more iterative, agile project methodology.

Technical Review 88

Technical Review Development Team Review 2013 Underperforming Technical Team 88

Binfire

DECEMBER 11, 2023

Online assessment tests have become inseparable parts of every organization, and their vital role has increased over the past couple of years. However, establishing a successful online assessment test is a challenging undertaking. This blog post will discuss how project management principles can improve online assessment results.

Development Team Review 78

Development Team Review Technical Review Software Review Monitoring 78

Scrum.org

JULY 29, 2019

Doesn't product quality interest the developers, as well as code health and the amount of technical debt hiding beneath the surface? Team health? Flow of work, from the time the team starts working on a Product Backlog item until your customer is using it? Invite your manager to the Sprint Review.

Technical Review 181

Technical Review Underperforming Technical Team Development Team Review Software Review 181

Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. But we can't ignore the differences in lingo.

SCRUM 123

SCRUM Development Team Review Technical Review Cadence 123

Scrum.org

DECEMBER 16, 2024

While Scrum excels in simplicity and flexibility, applying it out of the box often falls short in corporate contexts due to limitations in product discovery, scaling, and portfolio management. Also, having just one Scrum team is rare unless youre working for a startup in its infancy. Most of the time, multiple teams develop products.

SCRUM 167

SCRUM Technical Review Software Review Innovation 167

Scrum.org

AUGUST 17, 2020

A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. Increased software quality can be demonstrated by measurably less technical debt, fewer bugs, and less time spent on maintenance.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

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? Make use of today's technology and reach out to other Scrum Masters.

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Scrum.org

DECEMBER 9, 2018

This ‘seperate team’ pattern results in the ‘delivery sub-team’ being reduced to axe-grinding, code-wielding backlog lumberjacks (programmers & testers), do we want this? Research outside of the Scrum Team. A common scenario is where UX research is done outside of the Scrum team, or at least outside of the Development team.

SCRUM 173

SCRUM Agile Development Team Review Software Review 173

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 202

Underperforming Technical Team 2007 2006 2009 202

Planio

MAY 8, 2023

On average, IT projects come with more complexity and risk, and can quickly fall to pieces without proper due diligence, management, and leadership. with examples of IT projects) IT project management is the process of planning, organizing, running, and managing information technology projects. And that’s no simple job.

Technical Review 78

Technical Review Software Review Development Team Review Infrastructure 78

Project Bliss

MAY 24, 2017

In a waterfall approach all planning is done up front, and then the team executes according to the plan. A project manager leads the effort and works closely with the team to plan and execute the project. The team generally completes work in one phase before moving on to the next. Review and Adjust.

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

Scrum.org

JULY 10, 2018

Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The Development Teams need to be accountable for the quality of the product and how it's made. Technical risk - can it be made/build?

Risk Management 149

Risk Management Risk Technical Review Underperforming Technical Team 149

Scrum.org

OCTOBER 30, 2022

Although I’m not a highly technical guy, I have always worked closely with software development teams and the book contains so many great ideas that benefit development teams. In order to make the start as smooth as possible, you spend lots of time with the team to practice the Scrum kickstart.

SCRUM 213

SCRUM Development Team Review Closing Technical Review 213

Scrum.org

FEBRUARY 15, 2020

In the case of product development, there are a number of variables like people, process, technology, cultures, geographies, tools, skills, relationships, etc. Depending on the number of variables and variability within those variables, it is essential for teams or leaders to adapt their environment and style of decision making.

SCRUM 223

SCRUM Development Team Review 2012 Technical Review 223

The IIL Blog

OCTOBER 17, 2023

Agile team A cross-functional group of individuals (e.g., Product Owner, Scrum Master, Development team members) who work collaboratively to deliver value in an Agile project. Backlog A list of tasks, features, or requirements to be addressed by an agile project manager or team and is often associated with Agile methodologies.

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

Planio

OCTOBER 19, 2021

And whether you’re a designer, developer, team lead, or administrator, your job requires many of the same skills that separate the best project managers: organization, effective collaboration, and being goal-oriented. Phase 5: Closing. Step 12: Plan your first sprint as a team. Phase 5: Closing. Phase 2: Planning.

Technical Review 199

Technical Review Software Review Risk Management Estimate 199

Scrum.org

OCTOBER 7, 2019

Goodhart’s law states that a metric ceases to be a useful metric once it becomes a target, for example, for a performance review, because participants figure out how to game the system. However, it turns into the opposite if unleashed upon a less experienced team for productivity reporting purposes by the management.

Agile 194

Agile Underperforming Technical Team Estimate SCRUM 194

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 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. And classic teams only get to that level of “working” pretty infrequently.

Cadence 156

Cadence Development Team Review Technical Review Software Review 156

Project Bliss

MAY 10, 2017

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Working software is the primary measure of progress.

Software Developers 191

Software Developers Software Development Software Review Agile 191

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. And classic teams only get to that level of “working” pretty infrequently.

Cadence 150

Cadence Development Team Review Technical Review Software Review 150

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. Review and align your roadmap with other internal teams. Ask past users for reviews. OKRs are great for setting quarterly goals for your product roadmap and having a way to assess and judge their success. Increase repeat purchases.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148