Remove Blog Remove Cadence Remove Software Review Remove Technical Review
article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog.

article thumbnail

Benefits of Scaled Agile Framework ( SAFe®) – Agilemania

Agilemania

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

SAFe Simply Explained (Part 1): Core Competencies and Principles

Inloox

What usually started in software development can now be extended to the entire company and thus, change the way people collaborate. 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. But it’s not that easy.

article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

In this blog I want to share some common collaboration problems and solutions I experimented with. 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. Lack of product focus.

article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

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. See a recent blog post I wrote about this). Well, let's unpack this.

SCRUM 136
article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

article thumbnail

How Agile Practices Enable Remote Working

Scrum.org

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. We know Agile is not just for software teams. 4 – The Review. At the end of the sprint, after the Review, you have the Retrospective.

Agile 248