4 ms·

Sounds like Agile to me.

by joshwa 19y ago

emmett 19y ago
We don't share much with "agile development" except a rapid development cycle. "Agile development" things we don't do do (from the wikipedia article): Exhaustive unit and integration testing - our testing is sparse and only for things that need it worst Close, daily cooperation between business people and developers - getting business people involved in day to day development is horrible, at least in our experience Even late changes in requirements are welcomed - we don't really have "requirements" Face-to-face conversation is the best form of communication - face to face communication is essential, but it's not the "best form of communication". It's extremely costly in comparison to email. Although we are "agile" in the following ways, they seem so self-evident that it's difficult to think anyone would ever admit they don't follow them: Customer satisfaction by rapid, continuous delivery of useful software - vs. slow, halting delivery of useless software? Working software is delivered frequently (weeks rather than months) - this we do, and it's good advice. Small things we'll even do on an hourly, or minutely basis. Working software is the principal measure of progress - broken software or nonsoftware is the measure of progress? Projects are built around motivated individuals, who should be trusted - projects are built around commitees who can't be trusted? Continuous attention to technical excellence and good design - no attention to technical excellence or design? Simplicity - complexity? Self-organizing teams - top-down organized teams? unorganized? Regular adaptation to changing circumstances - rare adaptation to changing circumstances?
- abstractbill 19y ago
  Exhaustive unit and integration testing - our testing is sparse and only for things that need it worst Agreed, and I don't think we suffer for it. Something we do that has a bigger bang-for-buck imho is a lot of monitoring. Just about every one of our live systems gets automatically and regularly tested to make sure it's always working. I sleep better for knowing this.
  - gibsonf1 19y ago
    Is this why Hacker TV falls on a Thursday? (Testing day)
    - abstractbill 19y ago
      That's just a coincidence - we started Hacker TV before we settled into this weekly cycle.
- joshwa 19y ago
  Hmmn, maybe Daily Standups are a Scrum thing? I can never keep the various sects straight. That and last-minute release planning (the Product Backlog).
  - pchristensen 19y ago
    They don't belong to anyone, just consider it a good habit that may or may not work for you.

Sounds like Agile to me.

by joshwa 19y ago

Sounds like Agile to me.

We don't share much with "agile development" except a rapid development cycle. "Agile development" things we don't do do (from the wikipedia article): Exhaustive unit and integration testing - our testing is sparse and only for things that need it worst Close, daily cooperation between business people and developers - getting business people involved in day to day development is horrible, at least in our experience Even late changes in requirements are welcomed - we don't really have "requirements" Face-to-face conversation is the best form of communication - face to face communication is essential, but it's not the "best form of communication". It's extremely costly in comparison to email. Although we are "agile" in the following ways, they seem so self-evident that it's difficult to think anyone would ever admit they don't follow them: Customer satisfaction by rapid, continuous delivery of useful software - vs. slow, halting delivery of useless software? Working software is delivered frequently (weeks rather than months) - this we do, and it's good advice. Small things we'll even do on an hourly, or minutely basis. Working software is the principal measure of progress - broken software or nonsoftware is the measure of progress? Projects are built around motivated individuals, who should be trusted - projects are built around commitees who can't be trusted? Continuous attention to technical excellence and good design - no attention to technical excellence or design? Simplicity - complexity? Self-organizing teams - top-down organized teams? unorganized? Regular adaptation to changing circumstances - rare adaptation to changing circumstances?

abstractbill 19y ago
Exhaustive unit and integration testing - our testing is sparse and only for things that need it worst Agreed, and I don't think we suffer for it. Something we do that has a bigger bang-for-buck imho is a lot of monitoring. Just about every one of our live systems gets automatically and regularly tested to make sure it's always working. I sleep better for knowing this.
- gibsonf1 19y ago
  Is this why Hacker TV falls on a Thursday? (Testing day)
  - abstractbill 19y ago
    That's just a coincidence - we started Hacker TV before we settled into this weekly cycle.
joshwa 19y ago
Hmmn, maybe Daily Standups are a Scrum thing? I can never keep the various sects straight. That and last-minute release planning (the Product Backlog).
- pchristensen 19y ago
  They don't belong to anyone, just consider it a good habit that may or may not work for you.