Agile Pain Relief Notes from a Tool User

JULY 14, 2020

The goal of this post is to give teams a solid introduction on how to have not-sucky Sprint Retrospectives. Retrospectives are explicitly part of Scrum – “ The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.”

Agile 90

Agile SCRUM Weak Development Team Systems Review 90

Gorilla Logic

FEBRUARY 7, 2019

“ My Scrum Master scheduled all these meetings, but they are taking time away from my actual work!”. I’ve seen some people struggle with the amount of meetings that revolve around an Agile implementation, but these spaces where the team members come together are priceless. Scrum ceremonies are where the magic happens!

SCRUM 74

SCRUM Software Review Technical Review Weak Development Team 74

Accenture

OCTOBER 29, 2018

Once, over beers late into the evening in an old European pub not far from his office, an executive shared with me his personal Agile mindset transformation journey. It is an account that I have found representative of many when they begin to lead Business Agility transformation. But first, some background.

Agile 108

Agile Weak Development Team Coaching SCRUM 108

Agile Pain Relief Notes from a Tool User

OCTOBER 26, 2021

The World’s Smallest Online Bookstore team has just come out of their Sprint Review. For those who’re keeping score, the team committed to a Sprint Goal: Have basic reader review system in place so book buyers can see a variety of opinions about a book. The team return from lunch and the Retrospective starts.

SCRUM 52

SCRUM Examples Weak Development Team Software Review 52

Agile Pain Relief Notes from a Tool User

JUNE 22, 2022

When a product team starts work on a product, it’s important that they understand the vision. Over the process of a few hours these activities get the Developers and Customers to a common understanding of what problem they’re attempting to solve. Too often the answer is, “ To be Agile ”. Who is involved. Characteristics.

SCRUM 57

SCRUM Weak Development Team Agile Exercises 57

Agile Pain Relief Notes from a Tool User

NOVEMBER 22, 2021

Metrics tells you whether three days is how long it took one person (data) to unload a cubic yard (data) of rocks in a rainstorm, or whether it’s how long it took a team of five developers (data) to plan, create, test, and release a product that does X. But that’s a weak and easily gamed measure. manipulate) this number?

Weak Development Team 52

Weak Development Team Data SCRUM Metrics 52

Marcus Blankenship - Podcasts

JUNE 11, 2020

How can we train teams to consistently produce quality code without negatively impacting productivity? David Green, discuss Agile Dojos and how they can make teams more effective. Dojos provide a six-week training ground where teams focus on recognizing and replicating value by pairing, mobbing, and swarming. Episode 46.

Agile 59

Agile Software Review SCRUM Weak Development Team 59

Agile Pain Relief Notes from a Tool User

JANUARY 21, 2021

Let’s examine these successively abstract models: A little bit abstract: A team’s Task Board, Scrum Wall, or the overall Portfolio Kanban Wall. Small errors creep in if people forget to move items for a day, and other times what is happening in the team is more complex than the board can represent.

Report 83

Report Weak Development Team SCRUM eBook 83

Luis Goncalves

FEBRUARY 12, 2019

From a team of 30 people to now a giant tech corporation with over 70,000 employees, Google is one of the hallmarks of OKR as an organisational goal-setting methodology. The company used to adopt the “rank and yank” system wherein managers had to identify their least productive team members through a yearly evaluation. Take The Test.

Company 113

Company Weak Development Team SCRUM Coaching 113

Evolution4all

JULY 2, 2018

In one of his articles, Welch reiterated that budgeting hides opportunities for growth and at the same time, promotes bad behaviour especially when market demands change and the company still tries to reach its target. Furthermore, without a process to allocate funds properly, it will be easy for anyone to game the system.

Budget 183

Budget Innovation Weak Development Team Agile 183

Agile Pain Relief Notes from a Tool User

SEPTEMBER 28, 2022

Impact Mapping is a strategic tool to help teams and businesses focus their work on a product feature that will give the most bang for their buck. I’ve used Impact Maps for teams seeking to figure out what/where to build next, and I’ve also used them outside of software development. What can we do as a team to deliver the Goal?

Weak Development Team 93

Weak Development Team SCRUM Software Review Agile 93

Storm Consulting

MAY 3, 2018

London, UK 1 st May 2018 at Skills Matter , for Scrum Event. Agile Manifesto author and software expert Robert Martin asks if it is time for us to take responsibility for our work? Can we admit that Agile hasn’t worked? Wanna know how Uncle Bob really feels about Agile? There are those doing ‘ Scrum fall ’.

Software Review 56

Software Review SCRUM Industry Software 56

Codegiant

APRIL 3, 2020

Managing your team doesn’t have to be a mind-boggling task… Nor managing your projects should be an overwhelming burden. Yet, without a powerful agile project management software, you’ll have hard times getting your teammates on the same page. What’s more, Codegiant offers both Kanban and Scrum boards. You can create Roadmaps.

Project Management 52

Project Management Agile Tools Software Review 52

Accenture

APRIL 16, 2018

He had come on a ten-day trip to India to select an Indian offshore company to be his Agile provider for software development services. He had already met with many top software providers to learn about their ability to deliver high-quality software and demonstrate Agile software development capabilities.

Leadership 65

Leadership Weak Development Team Agile SCRUM 65

Agile Pain Relief Notes from a Tool User

DECEMBER 7, 2022

From working with Scrum and Kanban teams, I know that bonuses are counter-productive anywhere team members are doing knowledge work and their work is interdependent. The same might apply in other areas too, but I know this to be true in the context of software development in particular, because of my experience and study. “A

Agile 62

Agile Weak Development Team SCRUM Software Review 62

Altexsoft

DECEMBER 29, 2021

In software development, estimates have to be done to evaluate the duration and cost of the project and quite understandably, stakeholders want them to be as accurate and reliable as possible. Later, they were popularized by Mike Cohn and his book Agile Estimating and Planning published back in 2005. What are story points?

SCRUM 64

SCRUM Agile How To Software Review 64

Marcus Blankenship - Podcasts

APRIL 2, 2020

Is your team running so smoothly that it hums? In this episode of Programming Leadership, Marcus and his guest, Ron Lichty, discuss what makes high-performance teams versus what makes low-performance teams. Most teams already know which category they fall into, but the solution to a low-performing team isn’t always clear.

Weak Development Team 72

Weak Development Team Software Development Software Review Software 72

Marcus Blankenship - Podcasts

MARCH 4, 2020

Drawing on his 40 years in the software industry, GeePaw’s solution is to develop a thick culture in which certain standards are established across the industry. How the doubling rate resulted in a lack of leaders that can develop an industry discipline (6:34). Developing a common language of change in the trade (24:24).

Software Review 59

Software Review Software Technical Review Culture 59

Wolk Software Engineering

FEBRUARY 3, 2023

In Part I , I explored some of the most popular software development methodologies (SDM) to explain why they often fail to improve our outcomes. Kill” Scrum: Scrum has helped us to learn a lot, but it is time we move on. We need a new methodology that learns from the scrum ease of adoption.

Weak Development Team 52

Weak Development Team Technical Review Software Review SCRUM 52

Codegiant

AUGUST 15, 2021

While producing this blog post, I collaborated with our in-house software development team. And the very first question I shot their way was: “What are some of your biggest software development nightmares?” Deadlines are any software development team’s biggest nightmare. Trust me?—?new

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

AUGUST 15, 2021

While producing this blog post, I collaborated with our in-house software development team. And the very first question I shot their way was: “What are some of your biggest software development nightmares?” Deadlines are any software development team’s biggest nightmare.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Altexsoft

OCTOBER 25, 2019

This article will guide you through all the steps of a new product development (NPD) process and give you some insights into implementing best practices en route from a pure idea to roll-out and selling. What is a new product development process? Put together, these efforts compose a new product development (NPD) process.

Weak Development Team 73

Weak Development Team Innovation Development How To 73

Marcus Blankenship - Podcasts

JULY 9, 2020

In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. How Rich helps marketers/sales develop a more useful frame for engineering (10:01). Where does product management fit between sales and development? (26:31).

Weak Development Team 59

Weak Development Team Marketing Development Software Review 59

scruminc

MAY 10, 2022

Value Stream Management allows you to determine the measurable flow of value, where value delivery is slowed down, as well as create opportunities for better alignment & collaboration among teams. It’s a critical aspect of lean operations that contributes to the success of agile product development and delivery.

SCRUM 52

SCRUM Metrics Weak Development Team Organization 52

O'Reilly Media - Ideas

JANUARY 25, 2024

Before that, cloud computing itself took off in roughly 2010 (AWS was founded in 2006); and Agile goes back to 2000 (the Agile Manifesto dates back to 2001, Extreme Programming to 1999). Remember that these “units” are “viewed” by our users, who are largely professional software developers and programmers. What does this mean?

Trends 118

Trends Technical Review Technology Artificial Inteligence 118

LaunchDarkly

MAY 20, 2020

And I am a developer advocate for LaunchDarkly. It’s sometimes referred to as the bad apples management principle. If you have a team or a person who seems to be coincidentally associated with reliability issues, getting rid of that person is not likely to make the system more reliable. Watch Casey’s full talk.

Engineering 101

Engineering Weak Development Team Software Review Systems Review 101

Marcus Blankenship - Podcasts

JULY 9, 2020

In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. How Rich helps marketers/sales develop a more useful frame for engineering (10:01). Where does product management fit between sales and development? (26:31).

Weak Development Team 72

Weak Development Team Software Review Product Management Engineering 72

Crafty CTO

MAY 1, 2020

This is the sequel to my post Shape Up Your Agile , about the book Shape Up: Stop Running in Circles and Ship Work that Matters by Basecamp ’s Ryan Singer. We left off at the handoff of shaped, de-risked work to the development teams. In effect, we are saying: “Here you go, dev team. And shipping!)

Weak Development Team 52

Weak Development Team Software Review Course Agile 52

Codegiant

JULY 10, 2020

Moreover, Asana boasts Trello-like boards that will definitely bring valuable insights into your team’s progress. Why some teams love Asana is because of the transparency it can bring into their Asana workflows. Custom fields seem to be accessible across teams in your company. Loading times in Asana are as well poorly handled.

Software Review 52

Software Review UI/UX Project Management Technical Review 52

Strategy Driven

DECEMBER 3, 2019

These revolutionary developments required equally revolutionary changes, including more truly global firms, whole new industries, new ways of organizing enterprises (think first GM and then GE), new ways of working (email, virtual global teams), and more. agile studios), tools (communication such as Slack or Jira, etc.),

Weak Development Team 26

Weak Development Team Banking Real Estate Agile 26

Marcus Blankenship - Podcasts

OCTOBER 17, 2019

In this episode of Programming Leadership, Marcus and his guest Don Gray enlighten listeners regarding the world of software development, the reasons for implementing software changes and why it’s not as easy as people may think. Software development is not linear and not deterministic. Show Notes. Change is complex. Transcript.

Weak Development Team 40

Weak Development Team Systems Review Software Review System 40

Codegiant

NOVEMBER 9, 2020

From the desk of a brilliant weirdo #2 In this article, we will review 39 of the best software development and programming tools, ranging from web development and interactive development to rapid application development. Ability to plan agile work from project backlog to sprints. Features Team management tool.

Software Review 64

Software Review Tools Weak Development Team Development 64

Codegiant

NOVEMBER 9, 2020

From the desk of a brilliant weirdo #2 In this article, we will review 40 of the best software development and programming tools, ranging from web development and interactive development to rapid application development. Ability to plan agile work from project backlog to sprints. Features Team management tool.

Software Review 52

Software Review Weak Development Team Tools Development 52

LeanEssays

JULY 14, 2019

He describes “some surprising theories about software engineering”: I discuss these theories in terms of two fundamentally different development styles, the "cathedral" model of most of the commercial world versus the "bazaar" model of the Linux world. However, the open source world figured out a better way to develop software.

Software Review 91

Software Review Software Engineering Continuous Delivery Technical Review 91

Marcusoft

AUGUST 15, 2019

Agile is soon (?) I think the reason is that we have watered down the meaning of the concept by applying the name to more and more un-agile things. Soon we will be able to become agile without letting its ideas and principles changing a thing about what we do or how we act. And on LinkedIn I got even cockier and added.

Agile 65

Agile Weak Development Team KPI Meeting 65