| ... | ... | @@ -27,32 +27,25 @@ Some Scrum methods are used for production versions of large projects. |
|
|
|
|
|
|
|
### The Process
|
|
|
|
|
|
|
|
Generally one needs to design and tailor the agile process around the team, and some elements will vary on every single project.
|
|
|
|
|
|
|
|
What I have found is that you need to design and tailor the agile process around the team, and some elements vary on every single project.
|
|
|
|
We would still call what we follow today, Agile Software Development (using healthy doses of XP and SCRUM):
|
|
|
|
|
|
|
|
1. No one writes a line of code without a specification.
|
|
|
|
2. We divide every project as follows (Extreme programming terms on right):
|
|
|
|
- Project Name (Epic )
|
|
|
|
- Version (Iteration)
|
|
|
|
- Milestone (User Story)
|
|
|
|
- Issue (Task)
|
|
|
|
|
|
|
|
Today what I use I would still call Agile Software Development (using healthy doses of XP and SCRUM):
|
|
|
|
3. We have various fancy information radiators on this like unit testing, functional testing, behavior testing, continuous integration, etc.
|
|
|
|
4. Software versioning is intimately tied to the process and usually a trigger for the radiators.
|
|
|
|
|
|
|
|
No one writes a line of code without a specification.
|
|
|
|
5. Teams have a short meeting every single morning in which each developer goes over what (and how) they did yesterday, what they hope to get done today (and how) and ask any questions that they have.
|
|
|
|
|
|
|
|
We divide every project as follows (Extreme programming terms on right):
|
|
|
|
6. Milestones are usually two weeks long and we do make the deadline sacred at the expense of task completion (this can vary per milestone).
|
|
|
|
|
|
|
|
Project Name (Epic )
|
|
|
|
Version (Iteration)
|
|
|
|
Milestone (User Story)
|
|
|
|
Issue (Task)
|
|
|
|
7. All of these constructs (except the meetings) are managed through software and automation.
|
|
|
|
|
|
|
|
We have various fancy information radiators on this like unit testing, functional testing, behavior testing, continuous integration, etc.
|
|
|
|
|
|
|
|
Software versioning is intimately tied to the process and usually a trigger for the radiators.
|
|
|
|
|
|
|
|
Teams have a short meeting every single morning in which each developer goes over what (and how) they did yesterday, what they hope to get done today (and how) and ask any questions that they have.
|
|
|
|
|
|
|
|
Milestones are usually two weeks long and we do make the deadline sacred at the expense of task completion (this can vary per milestone).
|
|
|
|
|
|
|
|
All of these constructs (except the meetings) are managed through software and automation.
|
|
|
|
|
|
|
|
We also follow open coding standards for the languages we use and publish our own coding style guide which is based on open standards and well as some of my personal preferences.
|
|
|
|
|
|
|
|
Specifics aside, thats pretty much it.
|
|
|
|
8. We also follow open coding standards for the languages we use and publish our own coding style guide which is based on open standards and well as some the preferences of our senior software engineers.
|
|
|
|
|
