Giter Club home page Giter Club logo

Comments (2)

davebs avatar davebs commented on July 17, 2024 1

Yeah, those are good points.

I haven't read that blog post from 37signals but am a big fan of the company and many of their philosophies wrt organizing a business/project. Let me take a look. My current wording is awkward and could use a revision--I think yours is probably fine. Will leave it up here for a bit in case someone else wants to weigh in.

On the point of deployment/delivery at the end of an issue, my instinct is to be agnostic as to method. While there are many good arguments for continuous integration, I find there are reasons in practice for waiting on deployments and those reasons can vary a lot depending on the company/team/project. In these cases, I think it could make sense for "deploy to staging" or whatever to be an actual Issue in the sprint.

from agilelite.

miniscruff avatar miniscruff commented on July 17, 2024 1

I see your point on being agnostic on continuous integration, and how it ( probably ) extends to other tools and processes like test-driven development, pair programming, etc. There are always going to be companies or projects that may follow some but not all and that's totally fine. Delivering to users as a requirement would also go against workflows such as gitlabs release cadence and other timely releases.

Maybe one of these alternatives.

  • An issue is any unit of work that can be completed in its entirety within the sprint. ( this assumes there is some understanding of entirety for the team/project/company but that we are agnostic on what that is. )
  • An issue is any unit of work that can be completed based on your team/project/company standards.
  • An issue is any unit of work that can be completed within the sprint. ( just no extra statement about requirements )
  • An issue is any unit of work that can be completed in a single sprint, splitting if necessary. ( Can also include a small detail that favoring larger issues is ideal. )

I would still include the second sentence of being in the sprint or backlog, I think that is very important.

I think the difference here is all very minimal so whatever aligns more with your vision.

from agilelite.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.