CONTACT US 600 Park Offices Drive Suite 150 Research Triangle Park, NC 27709 support@dzone.com +1 (919) 678-0300
DZone
CONTACT US 600 Park Offices Drive Suite 150 Research Triangle Park, NC 27709 support@dzone.com +1 (919) 678-0300
Six Reasons Why You Need to Pay More Attention to the Sprint Goal - DZone
The Sprint Goal is an important part of Scrum. It's like a burning torch that unites the Development Team and helps it move forward during the Sprint. However, the Sprint Goal is not discussed very often, and in this article, I would like to talk about the deep importance of this component. First, let's look in the Scrum Guide and see how it describes the Sprint Goal. The Sprint Goal is an objecti
Scrum Myths: Scrum Conflicts With Fixed Dates - DZone
This is a very common myth, especially with people who develop software only within the context of a closed scope (i.e., a traditional project). The Scrum framework is agnostic when it comes to set the context of software development; it just talks about “complex product development.” In general, Agile software development avoids this concept of “project.” The Iron Triangle Software development is
Scrum Myth: You Can Only Release the Product at the End of the Sprint - DZone
One of the recurring Scrum Myth discussions I have with colleagues, teams new to Scrum and those attending training when comparing Scrum and DevOps relates to a misinterpretation of the following paragraph from the Scrum Guide. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.” It must be in useable
Continuous Delivery Anti-Patterns - DZone
This article is featured in the new DZone Guide to DevOps: Continuous Delivery and Automation, Volume IV. Get your free copy for more insightful articles, industry statistics, and more! An anti-pattern is typically a behavior that hinders or at least negatively influences a target objective. There are many anti-patterns for Continuous Delivery documented by people like Jez Humble, Steve Smith, and
Facilitating Effective Agile Retrospectives - DZone
This article is featured in the new DZone Guide to the Software Development Lifecycle: QA and Testing, Volume II. Get your free copy for more insightful articles, industry statistics, and more! Agile teams use retrospectives to reflect, learn, and adopt their way of working. Let's explore how you can do effective agile retrospectives and what facilitators can do to get more value out of them. An a
Agile Antipatterns - DZone
What is an antipattern? It's a pattern that you think will improve things, but actually, it does the opposite. It makes things worse. Sometimes this is visible and sometimes it isn't. The following is a list of antipatterns that I have observed. Backlog In Scrum, the purpose of a backlog is to give an idea of the work that is to be done for the project or product to make it a reality. At a high le
Kanban for Software Testing Teams
Kanban, a highly effective framework for “going agile,” is based on the Japanese business philosophy of kaizen, which believes that everything can be improved. One of the principles of kanban that makes it well-suited for agile delivery is that it only works if you commit to continuous improvement. Here, I’ll detail what kanban is, how to use it, and how your QA team can implement it right away. W
Managing Spring Boot Application
Spring Boot is a brand new application framework from Spring. It allows fabulously quick development and rapid prototyping (even including CLI). One of its main features is to work from single "uber jar" file. By "uber jar" I mean that all dependencies, even an application server like Tomcat or Jetty are packed into a single file. In that we can start web application by typing The only thing we're
20 Questions a New Scrum Master Should Ask Her Team to Get up to Speed - DZone
Start Learning the Ropes in 60 Minutes I was recently asked to participate in the product backlog grooming of a team that was looking for a new Scrum master. I was skeptical in the beginning. I had only limited knowledge about the project—a commercial website based on a CMS—, the grooming session was time-boxed to 60 minutes, and I hadn’t met the team members before beyond a very brief “hello”. So
Why Transparency is Essential for Collaborative Development - DZone
it’s easy to talk about collaboration. it’s something the clearvision team spends a lot of time thinking about — improving collaboration both internally and externally. it’s one of the key principles of agile working, and there are countless tools out there all designed to facilitate collaboration. just take a quick glance at the atlassian marketplace as an example, and you’ll see thousands of add
13 Things That Make a Good Build System
When recently looking for a replacement for our internal build system, I wrote out a wish list of what I wanted in a build system. This post will describe the thought process around that wish list and why eventually we decided CircleCi was the best solution that fit all these points. Existing Build SystemOur starting code was a single Java repository with dozens of submodules, but now includes Go
Code Commenting Patterns
Over the years, I have had the fortune to work with a modest list of companies and clientele. With each opportunity, I came into contact with a wide range of programmers - each with their own unique style. In fact, every project itself has had some element of uniqueness when compared to the others. I've found that the intersection of these qualities has trickled down into the program code that I o
Why Our DevOps Maturity Has Not Improved As Much As I Expected - DZone DevOps
One thing that continues to fascinate me is how after so many years I can still walk into IT organizations and see basic practices not being followed (e.g. Software Configuration Management or Continuous Integration or… ). Shouldn’t we all know better? I recently came across some slides from the late 90s and early 2000s that pretty much read like something that comes from a DevOps conference today
10 Signs When Projects Are Doomed to Failure - DZone
Are you working on a project, that runs badly? Have you ever asked yourself if your project is doomed to failure? In this blog, I will list 10 signs, that may help you to find out. Let me quickly tell you, who I am: I am working as an IT freelancer/consultant in the area of Java(TM) Enterprise Applications since 2000 and I must admit, that besides some successful projects, I also had to experience
Top 8 Reasons Why Agile Fails in Large Enterprises - DZone
Sanjay Zalavadia writes in an article for InfoQ that while Agile software development has proven to be a major benefit to various teams, it can affect businesses differently depending on their size and how they integrate the methodology into their operations. Zalavadia provides eight common areas which impact the adoption of agile development process in large enterprises: #1 - Lack of ClarityLarge
Top 10 KPIs You’ll See in a CEO’s Dashboard - DZone Agile
in a series of 26 interviews with ceos, the harvard business review identified 3 key issues which were worrying business leaders around the globe. a major challenge was finding and retaining the right staff, especially in today’s technologically complex world. another big worry was the impact of operating in a global market – navigating this context and keeping a company of thousands of individual
7 Signs You're Doing DevOps Wrong - DZone
in an article in infoworld, adam bertram takes a look at some of the most common misconceptions and flawed implementations of devops. chances are, your company has fallen prey to at least one of them so read on. sign no. 1: you need to buy “the devops” “devops” cannot be obtained overnight with a simple check and a little training. it is a transformational approach to core processes, and it takes
Microservice Registration and Discovery with Spring Cloud and Netflix's Eureka - DZone
Originally published by Josh Long, on the Spring blogThe microservice style of architecture is not so much about building individual services so much as it is making the interactions between services reliable and failure-tolerant. While the focus on these interactions is new, the need for that focus is not. We’ve long known that services don’t operate in a vacuum. Even before cloud economics, we k
Agile: Coaches or Consultants? - DZone Agile
The distinction is often made between agile adoption and agile transformation. The agile coach, from my experience, is often working at an intimate, team level; evangelizing, guiding, and embodying agile principles. When the entire enterprise is hoping to "transform", they need more than a coach; they need an agile consultant. No disrespect to agile coaches; many can and do perform enterprise evol
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
