Agilemania

DECEMBER 27, 2020

The articles also included why a Product Should care about the technical debt and allow the development team to refactor the code to control the technical debt. Previous articles of mine explained about, what is the technical debt and how this impacts the total cost of ownership. Anything that can be measured can be improved.

98

98

Cprime

MARCH 12, 2024

Here are a few that will make a world of difference: Simplify First and Refactor for Improved Code Quality – Often, you’re starting with something that hasn’t been cleaned up in a long while. Utilize AI to refactor code into smaller, more atomic functions, enhancing maintainability and quality.

Artificial Intelligence 52

Artificial Intelligence 52

Leading Agile

JANUARY 24, 2022

In this video, Mike Cottmeyer talks about the underpinnings of our approach and how it has evolved into a systematic way to refactor organizations at scale—and create the conditions where Agile can thrive and produce the best business outcomes.

Agile 62

Agile 62

Agilemania

OCTOBER 29, 2020

Over time, developers evolve on their technical skills and practices, which requires refactoring for the Products. When one says learning, this learning can be on the business side and the technical side. If not done or partially… The post Can the team avoid Technical Debt completely? appeared first on Agilemania.

75

75

Leading Agile

FEBRUARY 29, 2024

Unless you have been constantly refactoring and modernizing this asset over its history, problems begin to emerge: On-premises infrastructure costs are not competitive. Suppose you are a leader at a company that developed an important application over an extended timeframe: 10, 20, or even 30+ years. Perhaps it is sold to other companies.

Agile 139

Agile Government Finance Monitoring 139

Leading Agile

MAY 17, 2023

They always know that, if they refactor something, they didn’t break anything else. That is a HUGE part of what makes Agile teams faster. They can move fast and furiously through the code because they always know if they broke something. That allows them to keep the code clean, defect-free, and well-architected.

Agile 125

Agile Project Management 125

Cprime

MARCH 6, 2024

With CodeBoost, your teams gain the power to instantly create, modify, debug, refactor, and convert code at the click of a button. Our expert team provides rapid implementation including setting up the platform, training developers, and providing ongoing technical coaching to optimize adoption.

Innovation 101

Innovation Documentation Agile Planning 101

Agilemania

APRIL 10, 2020

When was the last time you write a code which is not protected with unit test / no refactoring? When was the last time you end up fixing a bug reported in a legacy codebase which is full of bad code? When was the last time you see a class with more than 100 lines of code? Sounds similar?

52

52

Cprime

OCTOBER 24, 2023

Refactoring may not be glamorous, but it improves the product. But neglected architecture and infrastructure absolutely affect what users experience. Symptoms of excessive technical debt include degraded performance, frequent outages, and scalability limits. These directly hurt customer satisfaction.

Product Management 52

Product Management Product Management User Experience Documentation 52

Leading Agile

SEPTEMBER 24, 2018

What if you’d like to become more proficient at refactoring? ” Then find some code that offers an opportunity to practice doing that, like the Gilded Rose refactoring kata. Then, practice a specific sequence of refactorings again and again until it becomes second-nature to you.

81

81

Leading Agile

JULY 7, 2021

So we did decouple the code, we refactor to have clear APIs, we create contract tasks or mocks. The reason you need help in getting there in many cases is because teams that are just forming and just getting used to some of these agile practices are not experts in refactoring and product extraction.

Business Architecture 63

Business Architecture Agile Skillset Planning 63

Roman Pichler

AUGUST 9, 2017

I would argue that every product owner should have at least a basic understanding of core concepts, such as, object orientation, design patterns and architecture principles, as well as agile development practices, such as, test-first, refactoring, and continuous integration.

UML 75

UML Artificial Intelligence Product Management Product Management 75

Cprime

JUNE 27, 2023

You can simplify your build process by removing unnecessary dependencies, refactoring code, or fine-tuning compiler settings. Build processes with too many steps are more complex and take longer to run. Therefore, keeping the build process simple can also help in optimizing build times. Use incremental builds and continuous integration.

52

52

Cprime

JULY 25, 2022

It is much more progressive for a team to refactor or re-architect their application to make it easier to deploy than it is to constantly struggle to achieve release automation. The automation of releases can be very difficult, especially with older applications.

52

52

Cprime

SEPTEMBER 3, 2021

Software products evolve through multiple releases by a process of accretion and refactoring (adding new features and re-writing existing logic to support the new features). The cost of change is much higher for hardware than for software.

Agile 52

Agile Planning 52

Leading Agile

JANUARY 31, 2019

If you’re struggling with helping your organization understand why introducing technical practices like collective code ownership, refactoring, pair programming, and test-driven development is such a crucial part of attaining business Agility; this podcast will help you build the case.

Agile 56

Agile 56

Roman Pichler

DECEMBER 4, 2018

I am not suggesting that you should necessarily spend a year or more refactoring your product, as Apple did. If a refactoring release is the right approach for you, then your product roadmap should reflect this: It should show a release dedicated to future-proofing the product and making the necessary technical changes.

Innovation 101

Innovation Digital User Experience Documentation 101

My Agile Partner

OCTOBER 2, 2023

Developers should not try to anticipate things, even if it means refactoring later. Simplicity: It is essential to think KISS (Keep It Simple, Stupid) and to develop only what is necessary. Feedback: Extreme Programming (XP) emphasizes the importance of delivering quickly to get feedback as early and as often as possible.

Agile 52

Agile Planning Project Management 52

Sisense

SEPTEMBER 30, 2020

We invested effort in creating a great design and refactoring a lot of the existing content we had into Markdown from the old format. New and refactored content: Much of what’s been added to the portal is entirely new, plus we refactored a lot of existing content, revalidating and updating it.

Documentation 52

Documentation Embedded Analytics User Experience Visualization 52

The Uncommon League

MARCH 10, 2020

The iterative nature of Agile development may lead to a frequent refactoring if the full scope of the system is not considered in the initial architecture and design,” Mary Lotz , PMP, director of engineering at Segue Technologies, writes. Without this refactoring, the system can suffer from a reduction in overall quality.”

Agile 84

Agile Project Management Planning Customer Experience 84

Leading Agile

FEBRUARY 22, 2021

So if your team is focused on building features but to get to the base camp you want, you need to have an automated build or you need to have some refactoring in order to get rid of some technical dependencies and an option would be to have the studio take that code, uplift that technology, and return it where it’s refactored, has tests around (..)

Digital 63

Digital Vision Government Agile 63

Leading Agile

APRIL 12, 2023

It just requires a bit of refactoring of the organization and some thoughtfulness about how you’re going to get there. The cool thing is, is that the principles that we’re applying at the team level are the same principles we’re going to apply at scale.

Agile 62

Agile Enterprise Architecture Government Product Management 62

Cprime

FEBRUARY 8, 2024

By streamlining processes like code documentation and refactoring, generative AI dramatically enhances efficiency and productivity. This technology excels in automating routine coding tasks, enabling developers to focus on more strategic aspects of their projects.

Innovation 102

Innovation Healthcare Digital Data Management 102

Leading Agile

NOVEMBER 17, 2020

So you can do some of that technology refactoring once you get past base camp two. So as we reorganize the organization and refactor the organization around these business areas and value areas, we need to make sure that the application infrastructure and the environment is set up to support that. – Yeah, sure.

Agile 95

Agile Government Business Architecture Digital 95

Leading Agile

MARCH 31, 2021

It is tempting to throw in the towel and say that encapsulating the value stream is impossible without refactoring the code to eliminate those dependencies, but the reality is that encapsulation of the value stream is still feasible in this scenario.

Agile 118

Agile Government Visualization 118

Leading Agile

SEPTEMBER 17, 2018

They didn’t “do TDD wrong,” as they were careful to follow the red-green-refactor pattern. Apparently, it wasn’t checked at the integration or functional levels, either. Therefore, TDD doesn’t work. Well, most of the time, anyway. At least, when it was necessary. No sense in going to extremes.

Banking 88

Banking 88

Astera

NOVEMBER 7, 2023

Additionally, making changes to the API after the code has been written may require significant refactoring. Pros and Cons of the Code First Approach Advantages: Rapid prototyping and quick iterations, leading to faster development cycles. Ideal for situations with unclear or changing requirements.

Documentation 52

Documentation Planning Agile User Experience 52

Leading Agile

DECEMBER 7, 2021

It requires refactoring old technology. As an industry, we need to stop simply inserting a few coaches into an organization and expecting change to happen. Change is more than just an implementation of Agile methodology. It requires executive buy-in. It requires demonstrable progress.

Agile 130

Agile Vision Change Management 130

Agile Velocity

FEBRUARY 12, 2020

However, teams often lack necessary skills to implement development best practices such as pair-programming, refactoring, Test-Driven Development, emergent architectures, and Agile automated deployment strategies. To be a market-responsive organization, the capabilities to deliver frequently and quickly get feedback are critical. .

Agile 68

Agile Vision 68

Cprime

SEPTEMBER 14, 2023

All this needs testing, regression testing, and code refactoring, which they expected; they could not anticipate the effort and amount of work required. For example, let’s assume the developers create a new feature and change several existing features during the sprint. So, the developers will need to add work items to the sprint backlog.

Planning 52

Planning Backlog Management Agile 52

Agile Velocity

FEBRUARY 12, 2020

However, teams often lack necessary skills to implement development best practices such as pair-programming, refactoring, Test-Driven Development, emergent architectures, and Agile automated deployment strategies. To be a market-responsive organization, the capabilities to deliver frequently and quickly get feedback are critical. .

Agile 57

Agile Vision 57

Agilemania

FEBRUARY 9, 2021

Refactoring is done. Code is manually tested in dev and test environments. All code is integrated frequently. Integration testing is performed. SonarQube check is run to determine the code metrics. Or for teams that are just starting, it can be elementary and minimalistic, for example: All acceptance criteria are met. Testing is done.

Finance 52

Finance Documentation Agile 52

My Agile Partner

OCTOBER 30, 2023

The team’s local concerns (other new functionality, defects, refactors, tech debt, and maintenance) are also in the backlog. During PI Planning, teams decompose Features into stories in the backlog and establish their PI Objectives. These stories reload the team backlog for the upcoming PI.

Agile 52

Agile Planning Visualization Finance 52

Leading Agile

APRIL 25, 2023

So just like you wouldn’t walk into a legacy mainframe platform that needs to have product extraction work done, legacy refactoring, legacy recovery kinds of things and just go, oh, okay, we’re screwed. We’re fundamentally refactoring organizations to be able to operate more effectively.

Digital Transformation 62

Digital Transformation Agile Digital Government 62

Leading Agile

OCTOBER 4, 2018

As far as teaching Scrum is concerned, the players would be constantly revisiting and refining their Backlog, constantly questioning their ideas, constantly refreshing their thinking, constantly collaborating, constantly “refactoring” their designs.

Agile 66

Agile Planning Vision Government 66

Agilemania

MARCH 3, 2022

Refactoring. This certification course helps create an understanding of the need for agile engineering practices and encourages participants to adopt them based on their organization’s context. What will you learn? . Here are the learning objectives of the CSD Certification course-. Learn about Lean, Agile, and Scrum. Collaboration.

Agile 52

Agile Project Management Planning 52

Cprime

JULY 8, 2022

Refactoring and design principles can be applied to both development and deployment. Tests should be automated so they can run continuously without compromising code quality. That way, changes are not only tested for functionality but also potential side effects.

Agile 52

Agile Documentation Monitoring Planning 52