Honeycomb

JULY 26, 2022

Is the system working? First, let’s talk about what makes a system “work.” If we don’t know that our system is running, then it’s not done. If we can’t find out how healthy our system is, we can’t give our stakeholders confidence that the system will continue functioning. What is instrumentation?

Software Review 52

Software Review Systems Review TDD Load Balancer 52

MagmaLabs

AUGUST 26, 2021

There are a ton of examples of how much software is around us: cooling systems, our cellphones, automatic doors, microphones, cars, traffic lights, etc. It is not something to be taken lightly, the future will be built by us developers and we sure want a good one, not one in which things from the past were easier to use. Refactor?-?Eliminate

Software Review 52

Software Review Software Development Weak Development Team Systems Review 52

Gorilla Logic

MAY 19, 2021

Outsourcing software development in nearby Latin America, a practice referred to as nearshoring, solves many of the challenges that come from working with development teams across the globe. Build the continuous integration, delivery, and performance testing that a DevOps or DevSecOps approach requires .

Software Review 94

Software Review Technical Review Software Development Team Review 94

Apiumhub

MAY 31, 2022

Behaviour Driven Development is a software methodology that allows us to define and develop the product based on the behaviour of the system. It was born out of the aforementioned need to be able to communicate the business side with development. Features, groupings of scenarios, should not exceed 10 scenarios.

Software Review 52

Software Review Weak Development Team Technical Review Systems Review 52

James Shore

OCTOBER 27, 2020

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Not just spending money—that’s comparatively easy—but making real, meaningful changes to organizational structures, systems, and behaviors.

Agile 132

Agile Software Review Coaching Weak Development Team 132

Apiumhub

JANUARY 6, 2020

Feature Toggles (often also referred to as Feature Flags) are a powerful technique, allowing teams to modify system behavior without changing code. This enables developers to take full control of their feature rollouts, dark launch, and roll back poorly performing features. Feature Flag driven development.

Software Review 70

Software Review Weak Development Team Technical Review Continuous Delivery 70

Agile Pain Relief Notes from a Tool User

JUNE 6, 2018

Demonstrates that in any system where there is a bottleneck, the rest of the system should be subordinated to the bottleneck until the bottleneck is cleared. Goldratt’s work is, in part, the basis for Kanban and also shows why, in a constrained situation, moving a Developer or Writer from their primary work to the constraint (e.g.

SCRUM 65

SCRUM Software Review How To Quality Assurance 65

LeanEssays

JULY 16, 2015

In the First Round Review article I'm Sorry, But Agile Won't Fix Your Products , Adam Pisoni, co-founder and former CTO of Yammer, contends that “While SCRUM did manage to rein in impulsive managers, it ended up being used more to exert tighter control over engineers’ work.” It means tests as code, infrastructure as code, deployment as code.

Agile 69

Agile Software Review Technical Review Microservices 69

James Shore

MARCH 12, 2021

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. What other tests do you need to write? How does this code fit into the rest of the system?

Programming 56

Programming Software Review Technical Review Test-Driven Development 56

Codegiant

AUGUST 15, 2021

Most of the time, these newly delivered features aren’t exactly the same as the wireframes or product comps due to a poor road-mapping process. And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Trust me?—?new

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Agile Pain Relief Notes from a Tool User

DECEMBER 9, 2019

In technical terms: through the entire system, not a description of the component layers or technical need ( as illustrated by the picture ). The three components of User Stories, often referred to as the three Cs , are: Conversations : Conversations that discuss the Story details and result in creating the acceptance criteria.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

James Shore

MARCH 23, 2021

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. The first culprit is usually test speed. The “Fast and Reliable Tests” section describes how.

Software Review 72

Software Review Weak Development Team Testing Continuous Integration 72

Agile Pain Relief Notes from a Tool User

JUNE 23, 2019

jpg'; import ReleaseBurnupSupportIssues from 'src/content/blog/scrum-production-support/images/Release-Burnup-Support-Issues.jpg'; Whenever you are building and deploying a complex system, there are always going to be bugs, defects, and unforeseen problems with usability commonly referred to as Production Support issues.

SCRUM 52

SCRUM Examples How To Systems Review 52

Agile Pain Relief Notes from a Tool User

JUNE 5, 2018

Once there is enough evidence to start (perhaps after 3-4 Sprints of collecting), share the data in a retrospective and ask the team two key questions: Theory of Constraints Demonstrates that in any system where there is a bottleneck, the rest of the system should be subordinated to the bottleneck until the bottleneck is cleared.

How To 52

How To Software Review SCRUM Quality Assurance 52

Codegiant

AUGUST 15, 2021

Most of the time, these newly delivered features aren’t exactly the same as the wireframes or product comps due to a poor road-mapping process. And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

AUGUST 15, 2021

Most of the time, these newly delivered features aren’t exactly the same as the wireframes or product comps due to a poor road-mapping process. And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

APRIL 14, 2020

The Agile methodology definition was introduced by 17 software developers gathered in Utah back in 2001. Since then, most people refer to Agile as the Agile Manifesto. Due to Agile’s highly encouraging face-to-face interaction , you can bring everybody on the same page. Dynamic Systems Development Method ?—?Since

Agile 52

Agile SCRUM Software Review Technical Review 52

Agile Pain Relief Notes from a Tool User

JUNE 24, 2019

Whenever you are building and deploying a complex system, there are always going to be bugs, defects, and unforeseen problems with usability — commonly referred to as Production Support issues. Most organizations that run these kinds of systems have helpdesks for users to raise these issues with.

SCRUM 49

SCRUM Examples How To Systems Review 49

James Shore

MAY 24, 2021

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. For complex systems, this often involves a secret management tool. File systems run out of space.

Software Review 69

Software Review DevOps Metrics Systems Review 69

James Shore

APRIL 26, 2021

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. Test-driven development encourages you to think about and improve your design at nearly every step.

Software Review 83

Software Review Technical Review Systems Review Weak Development Team 83

O'Reilly Media - Ideas

MARCH 1, 2023

Coding practices is a broad topic that encompasses a lot—software maintenance, test-driven development, maintaining legacy software, and pair programming are all subcategories. As our systems are growing ever larger, object-oriented programming’s importance seems secure.

Trends 144

Trends Technical Review Technology Software Review 144

James Shore

JUNE 7, 2021

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. For an excellent and practical guide to incident response, see Site Reliability Engineering: How Google Runs Production Systems [Beyer et al.

Analysis 72

Analysis Weak Development Team Software Review Systems Review 72

LeanEssays

JUNE 5, 2015

Instead, Modig and Ahlström demonstrate that lean is about flow efficiency – that is, the efficiency with which a unit of work (a flow unit) moves through the system. In my case, the dental system was focused on the efficiency of the lab’s milling machine – no doubt an expensive piece of equipment. Consider our dental experience.

Software Development 55

Software Development Software Review Software Development 55

James Shore

AUGUST 19, 2020

So, what allows me to do this—what allows me to do this show, this software development show every week, and what allows me to write this book—is the people who hire me for training and consulting. First, business analysts would interview stakeholders and document the system requirements. In theory, anyway.).

Agile 99

Agile Weak Development Team Development Team Review Development 99