|
Build Just Enough of a Feature with ATDD Developers have a tendency to overbuild their code. This is frequently due to not knowing exactly when they're done and not knowing how robust a feature needs to be. Acceptance test-driven development (ATDD) is a great way to avoid this practice because when the acceptance test passes, the developer knows they're done building that particular feature.
|
|
|
Leveraging Kubernetes as a Tester
Slideshow
Kubernetes is one of the fastest growing open source projects in history, and it's taking the DevOps world by storm. With so many resources being poured into this technology, it would be nice if there were some benefits for testing.
|
Glenn Buckholz
|
|
Agile Development: Focusing on the Health of Your Code In Scrum, the product owner and the ScrumMaster are supposed to drive sustainable development. But there's a third force missing from the formula: the health of the code itself. We often forget that our code is also a member of our team, and we have to be concerned about its health and well-being as much as any other team member. That means using practices to develop good code from the beginning.
|
|
|
Picking the Right Branch-Merge Strategy A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster.
|
|
|
Are you Agile or Fragile in Product Development?
Agile product management aligns the Product,
Technical and Marketing teams towards building customer-centric products faster
with a possibility to refine the product scope based on the market conditions.
|
|
|
Software Development: An Industry of Amateurs David Bernstein says the software industry is an industry of amateurs. It's a young field, and he doesn’t think it's yet graduated into a true profession. Here, David contrasts the software industry with other, more established fields, and he talks about what software professionals need to do in order for the industry to become accepted and esteemed.
|
|
|
Examining Cross-functionality Bias on Software Development Teams Cross-functionality means having all the necessary people and skills on one self-organizing team. Unfortunately, the execution of cross-functionality is often biased. The main traps we fall into are misunderstanding the value of specialization, hero worship, and not “walking the cross-functional talk” as organizations. Let’s examine each of these pitfalls in the hope that your teams may avoid them.
|
|
|
When Software Development Becomes a True Profession David Bernstein describes the software profession as an industry of amateurs. He argues that it does not yet have many of the things that a true profession has, such as a defined path of entry or good apprenticeship opportunities. A big reason is that computer programming hasn't been around as long as other industries, but what else will it take for software to rise in the ranks?
|
|
|
Supporting Continuous Testing with Automation Create tests that can be used in a continuous testing environment, build the right number of tests, and don’t fall victim to the mistaken belief that everything can be automated.
|
|
|
All Customers Are Not Created Equal Software developers may not think they have much to do with customers, but it is wise to consider the customer in all you do, from collecting requirements to design and implementation.
|
|