Today was the last day of Software Architect 2012. Last day was dedicated to workshops and I decided to join Allen Holub session: “Agile/OO design from start to finish”. After these days I become a fan of A. Holub and I hope that I will be able to implement a correct OO design. It is pretty challenging, but I promise that I will try to write about this in future.
Here are some notes from the presentation that I considered important. A part of them are well known by all of you:
Agile is based on communication, but there are people that will not be able to integrate in a team environment. Even if they are great on technical side and have a lot of knowledge, they are not able to communicate and to share data. Sharing is one of the most important things in Agile. The biggest enemy for Agile is EGO. Because of this people will not be able to communicate and different roles will appear – “I am the MASTER and the team need to do as I say.” – WRONG.
When we are talking about user-stories, management should understand the concept of points and the relations between points and duration – there is no relationship. Also when the team say, there are 50% percent chances to not be able to finish at time, than the chances are pretty high.
If you have a bunch of user-stories, start with the one that are the most risky. You will need time to clarify and resolve them. Also if you have a complicate or a user story that is very big than you should slit him? One good solution here is for the first sprint to consider only one happy flow, after that another, or an exceptional flow and so on. In this way we will be able to make it more and more complex at each iteration. Your scope is to have something that is fully functional at the end of every iteration.
Be strong and in the moment when someone wants to take off a man from the team say “NO!” This action can affect the project velocity; because of this there are chances not to finish all the user stories at the end of the iteration.
I didn’t use the SCRUM and SPRINT terminology. Why? SCRUM is not the only way to be AGILE. From some perspective SCRUM is not agile, in the current “implementation”.
I will finish this post blogs about this conference with two cited that I heard today and I like:
“A ‘bug’ is not a logic error; it is a missing unit test.”
“Each team member is responsible for his own word and the team is responsible for the entire project (all the code and artifacts that are generated).”
Agile is based on communication, but there are people that will not be able to integrate in a team environment. Even if they are great on technical side and have a lot of knowledge, they are not able to communicate and to share data. Sharing is one of the most important things in Agile. The biggest enemy for Agile is EGO. Because of this people will not be able to communicate and different roles will appear – “I am the MASTER and the team need to do as I say.” – WRONG.
When we are talking about user-stories, management should understand the concept of points and the relations between points and duration – there is no relationship. Also when the team say, there are 50% percent chances to not be able to finish at time, than the chances are pretty high.
If you have a bunch of user-stories, start with the one that are the most risky. You will need time to clarify and resolve them. Also if you have a complicate or a user story that is very big than you should slit him? One good solution here is for the first sprint to consider only one happy flow, after that another, or an exceptional flow and so on. In this way we will be able to make it more and more complex at each iteration. Your scope is to have something that is fully functional at the end of every iteration.
Be strong and in the moment when someone wants to take off a man from the team say “NO!” This action can affect the project velocity; because of this there are chances not to finish all the user stories at the end of the iteration.
I didn’t use the SCRUM and SPRINT terminology. Why? SCRUM is not the only way to be AGILE. From some perspective SCRUM is not agile, in the current “implementation”.
I will finish this post blogs about this conference with two cited that I heard today and I like:
“A ‘bug’ is not a logic error; it is a missing unit test.”
“Each team member is responsible for his own word and the team is responsible for the entire project (all the code and artifacts that are generated).”
Comments
Post a Comment