In generic terms: Plan --> Do --> Asses (test) --> Act (adapt) --> repeat
In Agile Scrum terms: Adapt --> Scrum --> Inspect --> Scrum --> repeat
At the center of both of these cycles is transparency.
What can be useful is to send a tracer through the concept. A tracer is like a tracer bullet -- it is something that can mover through all of the complexity of your process and be seen within each step.
Build / Run
The build / run concept says have one team totally focused on new development (build) and one team totally focused on operational issues, help, day-to-day (run). The problem with this is that most developers want to be on the build team and the run team doesn't encourage growth. The solution is to rotate members in and out of both teams. Being on the run team should always be a temporary condition.
When does the traditional waterfall method work?
1. when you are working with known technology
2. when the components are stable and standardized
3. when the requirements are complete and unchanging
4. when the process is highly repeatable (you do it a lot)
Velocity
In agile scrum velocity means the average number of story points divided by sprints. In other words: on average how many stories do you cover per sprint?
Refactoring
Rewriting code without changing the functionality. This lets you clean up the inefficient code that results from constantly adding new functionality. It allows the developer to redesign without input from the business as the functionality must remain the same. "Rework is better than no work"
User Stories
The 3Cs of user stories:
Card - the story should fit on an index card
Conversation - the story is a commitment to a conversation/negotiation
Confirmation - you need to know the acceptance criteria for the solution
No comments:
Post a Comment