Planio

MAY 27, 2020

Without a clear definition of done , your development team doesn’t know what they’re working towards, your stakeholders are free to increase the scope, and your users most likely end up with a product that’s cluttered, confusing, and unusable. When can the development team change the definition of done (and how should they do it?).

Software Review 145

Software Review Technical Review Development Team Review Defining 145

Agilemania

OCTOBER 31, 2022

As software expands its wings in all industries, the demand for skilled product managers continues to grow. The role and responsibilities of the product owner includes identifying the business needs & market opportunities, establishing project objectives, and managing the product development process from ideation to final release.

Certification 98

Certification 2022 Underperforming Technical Team Lean 98

Leading Agile

JULY 3, 2023

As more and more companies scramble to untangle the code of their monolithic legacy software and get it into the cloud, strategic priorities are shifting. Want the Deck Text HIDDEN to 33777 Video Transcript We will run into times where packing software makes it harder for us to transform the skills of our staff and external vendors.

Software Review 125

Software Review Fractional CTO Technical Review Agile 125

Scrum.org

MAY 4, 2020

We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. Do you want to get this article in your inbox?

SCRUM 164

SCRUM Agile Technical Review Development Team Review 164

Leading Answers

MARCH 7, 2019

Designing something is typically a consensus-gathering and problem-solving exercise. Consider the process of designing a new car or home. The process is likely to be iterative and adaptive. Then, once the design is agreed upon, the process of production is typically more defined and repeatable.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Agilemania

NOVEMBER 11, 2022

Keep reading to find out more about this essential role in your company’s software development team. A Scrum Master is a facilitator who helps a Scrum team to self-organize, collaborate, and continuously improve. Facilitating daily stand-up meetings with the team. Providing feedback to the team.

SCRUM 88

SCRUM Certification Technical Review Lean 88

Scrum.org

AUGUST 8, 2018

A great position to support Scrum.org in fulfilling its mission of improving the profession of software delivery. The article “ The Making of the PSM-II Class ” describes the road towards and process of creating the class, this blog post will focus on the content of the class itself. How can we improve how we inspect and adapt?)

SCRUM 72

SCRUM Development Team Review Certification Agile 72

Wrike

NOVEMBER 10, 2020

Construction project managers also manage soliciting and leveling bids for the different parts of the project — preparing budgets and schedules for project phases, and managing the permitting process by coordinating with the authorities. What does a project manager do in software? A daily wrap-up routine. Monthly wrap-ups.

Technical Review 74

Technical Review Software Review Construction Development Team Review 74

LiquidPlanner

MAY 15, 2018

Business teams struggled with understanding their role in a software project while trying to sort through all the technical jargon used to build a website. Related: Adopting Agile is an Exercise in Change Management. Related: Agile Team Transitions are Not Always Textbook. Second Chance.

Agile 74

Agile Software Review Technical Review Development Team Review 74

Planio

DECEMBER 14, 2018

Sprints are the backbone of any good Agile development team. But maybe more than that, sprint planning aligns the development team with the product owner. Like any relationship, the one between you and your team requires communication and clarity. Step 1: Review your product roadmap. Download This Template.

Software Review 107

Software Review Planning Technical Review Development Team Review 107

International Institute for Learning

JUNE 22, 2022

The transformation impacted more than 500 research and development teams at Ericsson’s Business Unit Networks. I believe that to drive successful transformation, you need to focus on these key areas: vision, leadership, people, management, skills & capabilities, communication, processes and tools.

Telecoms 52

Telecoms 2022 Lean Development Team Review 52

nTask

DECEMBER 2, 2020

Such agile retrospectives help to improve processes, methods, and teamwork. The agile retrospective comes from the 12 th principle in the agile manifesto which states: “ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Aid your Team to Learn and Develop.

Agile 113

Agile 2020 SCRUM Software Review 113

Planio

MAY 18, 2021

While many teams start by building an MVP (minimum viable product) to get feedback, there’s another option. Agile planning is a process for reconciling your long-term product vision with the inevitable near-term iterations that will influence its development. Review and update your Agile roadmap every few months.

Agile 78

Agile Planning Influencer Initiating 78

Leading Agile

MARCH 15, 2023

And you’re able to get not only feedback from how customers are actually using the software that you’ve brought to market, but you’re also able to start deriving value from it. Like if they could just be heads down, write the software in layers, right?

Agile 62

Agile Development Team Review Software Risk Management 62

Planio

DECEMBER 5, 2022

To truly understand team rituals, let’s break that down into more detail. Each team ritual has to be named and have its own identity. Whether it’s a particular meeting, fun activity, or team bonding exercise, each ritual should have a name that it’s known by. Rituals are named. Rituals are templated.

Underperforming Technical Team 146

Underperforming Technical Team Software Review Energy Defining 146

MPUG

JULY 15, 2019

Now, imagine a software development project. The process is a complex one with many stakeholders involved over months, sometimes years. In this process, written requirements with written words are many times inadequate, sometimes even inaccurate, and most of the time said requirements don’t convey the real intent.

Agile 99

Agile Software Review Infrastructure Estimate 99

Leading Answers

JUNE 14, 2018

Can the average organization actually become a disruptive leader just by adopting the structures, tools and processes from the real disruptive leaders? Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development.

Technical Review 116

Technical Review Agile Lean Sustainability 116

Scrum.org

FEBRUARY 25, 2024

Providing the content was a simple process and only took a few minutes. I was surprised that ChatGPT did not require some processing time, as it claimed it would be immediately available. Group them into categories such as culture, process, or organizational structure.

SCRUM 175

SCRUM ChatGPT Technical Review Development Team Review 175

Leading Answers

JUNE 14, 2018

Can the average organization actually become a disruptive leader just by adopting the structures, tools and processes from the real disruptive leaders? Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development.

Technical Review 60

Technical Review Agile Lean Sustainability 60

Scrum.org

SEPTEMBER 13, 2021

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Scrum Anti-Patterns: From Product Backlog to Sprint Review. Development teams often create tasks an engineer can finish within a day.

SCRUM 197

SCRUM Underperforming Technical Team Development Team Review 2020 197

Scrum.org

NOVEMBER 27, 2018

This picture underscores the most essential rule in Scrum: create “Done” software every Sprint. But many teams struggle with this rule. An increment is considered “Done” by the Development Team, but requires further testing and stabilization in the next Sprint. It is tempting to fall into “shades of Done”.

Software Review 145

Software Review Technical Review SCRUM Software 145

Scrum.org

JANUARY 9, 2023

Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team?

ChatGPT 216

ChatGPT SCRUM Underperforming Technical Team Technical Review 216

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. This first set of the Scrum Master theses addresses their role in the Scrum process: Scrum is not a methodology, but a framework. Being a Scrum Master does not entail, and should never entail, enforcing processes.

SCRUM 224

SCRUM Underperforming Technical Team Technical Review Software Review 224

Scrum.org

FEBRUARY 9, 2022

That year, a group of 17 software practitioners looking for a better way to deliver software settled on the the term agile to refer to their more rational, human approach to complex work. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. It's an incremental approach.

Agile 244

Agile Software Review Technical Review SCRUM 244

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. And unfortunately, too many teams treat roadmapping like just another project, leaving it behind to collect dust as they move on and start building software. Why you need a roadmap (even as an agile team). Basic product roadmap example.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Planio

AUGUST 1, 2023

6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. A successful strategy isn’t a set-and-forget exercise. A successful strategy isn’t a set-and-forget exercise.

Development Team Review 78

Development Team Review Infrastructure Software Review Governance 78

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. Start a “Scrum Question of the Week” exercise. At the start of the week, you offer the team a question about the Scrum theory & principles. Things to try….

SCRUM 169

SCRUM Development Team Review Technical Review Consulting 169

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business. Bring in ongoing training.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Scrum.org

OCTOBER 19, 2020

This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum. There are no leadership roles in the Development Team. Not necessarily.

SCRUM 160

SCRUM Underperforming Technical Team Software Review Development Team Review 160

Planio

APRIL 6, 2021

A product requirements document (PRD) is one of the most important documents for teams using traditional project management. However, an increasing number of Agile teams are starting to see the value of adding more planning to their process. For example, who’s on the team? At first, this seems counter-intuitive.

Lean 78

Lean Technical Review Software Review Underperforming Technical Team 78

Wrike

MARCH 23, 2021

With so many diverse sets of interdisciplinary team members working with each other in the Agile Release Train, establishing a solid level of trust can help. Agile Release Train, also known as ART for short, is a set of the key people who are tasked with implementing, deploying, and releasing the particular hardware or software virtually.

Agile 36

Agile Planning Development Team Review Software Review 36

Leading Agile

OCTOBER 10, 2018

I was showing their development teams how to automate functional tests using Cucumber. During a workshop for one of the teams, I learned they did not write or maintain application code. As they were working through the hands-on exercises, their lead Business Analyst asked, “Can Cucumber read Excel files?”

Technical Review 96

Technical Review Software Review Underperforming Technical Team Engineering 96

Leading Agile

MARCH 17, 2021

And then the process developed a point of view around kind of why companies were jacking it up. They have the ability to produce work infested increments software, and they do sprint planning. They do daily stand-ups, they do reviews and retrospectives. It was just why agile fails. They do, right?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Project Pulse Journal

APRIL 16, 2024

Let us now check the world of T-shirt sizing - one of the project management tools that promises to streamline your planning process and transform it into an engaging, team-building exercise. Fosters Collaboration - It encourages team discussion and consensus, as team members must agree on the relative sizing of tasks.

Agile 52

Agile Technical Review Software Review Development Team Review 52

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Preparing test data to exercise applications prior to deployment. Automate what?

Software Review 78

Software Review Software Technical Review Development Team Review 78

Binfire

MARCH 13, 2017

What processes and technologies we will use to make the product? Is the product or service developed entirely in house or we will use outside contractors? A baseball coach knows or learns the strength and weakness of each team member and his team. What is the project’s ultimate goal? How much it should cost?

Underperforming Technical Team 154

Underperforming Technical Team Project Life Cycle Software Review Technical Review 154