作者彙整: Isaac Sacolick

Agile software development is not just about agile principles and practices. To be successful in releasing software that positively impacts end-users, addresses technical debt, and deploys reliably, the development team must also consider their agility-driving coding practices and architecture standards.

An even more important consideration is at stake for technology organizations. As hard as it is to develop software, it’s even harder to deploy enhancements and upgrades regularly over an extended period. Devops CI/CD and IAC (infrastructure as code) practices partially address one critical factor as the automation enables reliable and repeatable ways to deploy applications. Add in continuous testing, and development teams have a way to validate that code changes don’t impact existing functionality.

To read this article in full, please click here

(Insider Story) 閱讀全文 →

I recently participated in an #IDGTECHTalk, a Twitter chat held Thursdays at 12 pm ET that focused on the topic of “The Current and Future State of Coding.” Many of the questions and tweets were about coding languages and frameworks; I elected to focus on the role of software development management in ensuring teams meet objectives, follow best practices, and collaborate on solutions.

Many organizations empower self-organizing teams to commit every sprint and deliver reliable application releases. They expect code that is high quality, low defect, secure, and maintainable, that also meets business objectives and reduces technical debt. Large organizations that have multiple agile teams and strive to balance standards with self-organizing principles must consider the roles and responsibilities of management and key team members.

To read this article in full, please click here

(Insider Story) 閱讀全文 →

Development organizations sensing the shift from user-driven to machine-driven access patterns in APIs and services should consider event-driven architectures. These architectures enable the decoupling of rule-based services to microservices that consu… 閱讀全文 →

Fundamentally, agile user stories are short, simple tools to document a single action or intention desired by the targeted user to achieve a goal. The simplest user stories have a format, “As a user type or role, I want to action or intent so that reason or benefit” that answers at least three simple questions on who, what, and why the story is in the backlog queue.

As teams mature and organizations use agile across multiple teams and initiatives, agile user stories often take on a lot more definition and structure to ensure there is a shared understanding of the intent and underlying requirements.

Getting started with writing agile user stories

There are plenty of resources to help new product owners, business analysts, scrum masters, and technical leads to understand the basics of writing user stories. Some places to start include articles from Atlassian, FreeCodeCamp, Agile Modeling, and these 200 user story examples. One of the more complete writeups is in Alexander Cowan’s best agile user story. There are books on story writing, including User Story Mapping by Jeff Paton and Peter Economy and User Stories Applied by Mike Cohn. You can also take courses on story writing from Udemy, Learning Tree, VersionOne, and Lynda.

To read this article in full, please click here

(Insider Story) 閱讀全文 →

Fundamentally, agile user stories are short, simple tools to document a single action or intention desired by the targeted user to achieve a goal. The simplest user stories have a format, “As a user type or role, I want to action or intent so that reason or benefit” that answers at least three simple questions on who, what, and why the story is in the backlog queue.

As teams mature and organizations use agile across multiple teams and initiatives, agile user stories often take on a lot more definition and structure to ensure there is a shared understanding of the intent and underlying requirements.

Getting started with writing agile user stories

There are plenty of resources to help new product owners, business analysts, scrum masters, and technical leads to understand the basics of writing user stories. Some places to start include articles from Atlassian, FreeCodeCamp, Agile Modeling, and these 200 user story examples. One of the more complete writeups is in Alexander Cowan’s best agile user story. There are books on story writing, including User Story Mapping by Jeff Paton and Peter Economy and User Stories Applied by Mike Cohn. You can also take courses on story writing from Udemy, Learning Tree, VersionOne, and Lynda.

To read this article in full, please click here

(Insider Story) 閱讀全文 →