Archive for Work
One for the team
Posted by: | CommentsAs a ScrumMaster I am really sold on the Agile methodology. My enthusiasm can create angst for the team. I am really proud of the team I am working with right now. They have overcome many obstacles and really embrace Agile. They do not have a “cargo cult” mindset but a real commitment to be the most productive team in the company.
The team is willing to be a leader and will take on the risks. Because of this can do mentality I wanted to have all who were interested to view our first sprint demo. So what I did was use the largest distribution list for our department for our invitation list. Well this was a mistake and really caused the team to become very uneasy. They pointed out that we had overcome many obstacles in this sprint but there was not really much to show for it in the demo. We have completed one user story well and it is “done” according to our new standards of acceptance but it was only one user story.
They were correct. Perception is everything and we only have a “simple” user story to display for all of our work the last 3 weeks. The extended stake holders would not really understand what was involved in what we accomplished.
So I canceled the original meeting and invited a much smaller group to stake holders to the sprint demo. A lesson learned on consulting the team before make a major decision on who to invite to our sprint review.
Team Building and Focus
Posted by: | CommentsWhen there is a lack of focus this is a lack of teamwork. When each developer has other projects to work on they are not working together.
In an Agile team it is critical that each member has the same vision and goal. Unless the team is first the team will not succeed. When team members are more concerned about their own individual gaols instead of team goals you have lost the team focus.
Unless we can all capture the same vision we will fail. Oh, we may get a product out the door but will it be the best product we could have produced if we were focus.
In order to produce quality team work and capture the vision we have to spend quantity time together. This means working side by side with each other for hours a day. Time spent together ends up creating a team works together well an helps keep them focused on the vision.
Multi-tasking verse Single-task (part 2)
Posted by: | CommentsWhy do managers believe that they are getting more productivity from a person if they are working on multiple projects? I know they are afraid of have “down” time. But what really happens when a person has some down time?
Let me give you an analogy. Let’s say you by a new delivery van (yes we need to help the economy right now) and you want to start using it in your business. Now you want to make the most of this asset. So you decide that you will drive it at 100 miles hour and that you will not take it into the shop for routine maintenance because you will not be able to make deliveries with it. How long would your new new delivery van last? Is this the best use of your new asset?
Developers cannot be constantly running at peak speeds. Eventually they will wear out. Also, they need to be able to work on skill improvement and have a chance to expand their horizons. Slack time in the schedule is important just for the sake of sanity.
Having a developer working on multiple projects is bound to wear them out. This can be displayed in lack of enthusiasm, increase sick days or just plain bad attitude.
Self organizing as a team
Posted by: | CommentsHave we paralyzed our workers so they do not have any initiative? I recently started forming a new team and ran into several issues. We defined a product backlog and tasks to be done in this sprint. When the planning was finished the tasks that an engineer thought he was going to work on were removed from the sprint. Mind you there is enough work to do in this sprint to keep the team busy. This engineer though he had nothing to do because his tasks were removed. Then the resource manager was upset because they had put the member on the team and they had nothing to do.
This is prime example of the individual not thinking as a team member. This individual must realize they are a member of a team whose goal is to produce a successful product. We need to adjust to the needs of the team.
Agile at work
Posted by: | CommentsWe are now entering a phase at work where all of our projects are going to the Scrum methodology. I am not sure the people heading this up really understand how the methodology is to be used.
I know the my immediate manager has real concerns about the approach we are taking. His real concern is that we are setting ourselves up for failure.