|
snorkie wrote:
2. About half of the 15 minute morning morning consists of, "Lets have a Meet After to Discuss".
Reminds me of one of the Google commercials.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
SCRUM, it would seem, was derived from SCAM, SCRAP, or more likely, SCROTUM.
Just sayin' . . .
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
LOL 
|
|
|
|
|
As I heard it, scrum comes from rugby. Like in American football, the team goes into a huddle. Rugby, it is called a scrum.
|
|
|
|
|
What you need is a simple to understand definition[^].
SCRUM works, and works well, as long as you accept it. The greatest impediment is members of the team trying to work around or outside of the sprint. Once that happens things go FUBAR.
The stand-up has three questions - "What did you do yesterday? What will you do today? What help will need?" - anything outside of this does not belong in the stand-up.
speramus in juniperus
|
|
|
|
|
SCRUM works, and works well, as long as you accept it.
That's what my pastor told me about religion.
Religion works, and works well, as long as you accept it.
Interesting....
|
|
|
|
|
No matter how you call your "product development strategy/process", some people just prefer wasting time to actually doing their jobs.
|
|
|
|
|
snorkie wrote: 2. About half of the 15 minute morning morning consists of, "Lets have a Meet After to Discuss". Half the team stays after the meeting every day. How about just discussing it now and getting it over with?
One of the big purposes of SCRUM is to communicate amongst the team members, including with a stakeholder representative. One of the features of this is the very important detail of communication. If you are triggering something where people realize that a subgroup needs to meet every day about some detail, then this aspect of scrum is working the way it should.
This also keeps the stakeholder aware that there are problems to be solved, and they are being solved or at least identified. This goes a long way in avoiding surprises towards the end of the project.
You need to give it more time.
Windows 8 is the resurrected version of Microsoft Bob. The only thing missing is the Fisher-Price logo.
- Harvey
|
|
|
|
|
I'll give it more time, cause I like my job! However, I have yet to personally realize benefits from SCRUM. I feel that valuable communication is lost because the meeting is limited to the three questions. I feel like I'm living in a law drama where developers are lawyers having to have sidebars all of the time. We're all friends here, and can discuss issues in front of everybody.
Hogan
|
|
|
|
|
There should be nothing stopping you from talking to your colleagues outside of the stand up to further discuss issues.
If there are things which are a problem and could stop the team delivering working software then the standup is the place to raise this since everybody who is interested in the project succeeding should be there, however, it isn't the place for a full blown discussion of an issues.
One of the main things about any agile process is visibility into what's happening, so what work people are doing, how the project is progressing, problems, etc but depending on size of your team(s) not everybody present may need to participate in discussions about specifics so having "sidebars" is the right thing to do.
|
|
|
|
|
nathans.dropbox@googlemail.com wrote: One of the main things about any agile process is visibility into what's
happening
I haven't seen any popularized process control methodology where that wasn't a goal as well.
|
|
|
|
|
On top of other answers, it seems like issue with either team or definition of done/planning:
- is your team ( i mean team: devs, testers and writers) sitting in one room? IF not, try to sit them down close to each other. They will have a plenty of opportunities to communicate outside stand-up. Helps a lot.
- keep rigor on stand-up - just 3 questions, status and go to after discussions. I've seen failed introductions of SCRUM just because stand-ups got too long and people were just tired of too long status meetings
- items - seems like stuff is little too complex, task granularity is too large or guys do not have much experience... whatever, I can only guess. Try out with one-two items, split it into really small tasks with clear definition of done, see if it reduces number of after stand-up discussions. Be aware - SCRUM is also about constant code refactoring, sometimes it's even 3rd or 4th iteration on the same part of code, that produces functionality satisfying most requirements.
One person brought up important topic - open talk about one's problems. It takes experienced/good at 'soft skills' moderator to make team comfortable about telling of own flaws and drawbacks. Just one rule, yet very important - never allow it to have at least shadow of getting personal, always cut to the chase and disregard/ignore comments outside of subject.
There is no magic, golden triangle quality/time/cost requires constant corrective actions, be it cutting the scope or extending the deadline or decision like 'now we need to refactor to get better performance/make more extendible architecture'. Keep focused on use cases, which constitue 80%-90% of normal usage of software, patch corner cases or just avoid them by design limiting delivered functionality - from my experience developers tend to spend a lot of time (and cost in company terms) to cover all cases possible, instead focusing on the basic ones.
|
|
|
|
|
Michał Rybiński wrote: One person brought up important topic...
However all of those comments are appropriate to any business meeting and is not specific to SCRUM nor even any process methodology.
|
|
|
|
|
In SCRUM meetings, and particularly during retrospective after sprint, it is critical to ensure open, safe comm. That's why team has right to ask everyone else out during retrospective or ask executives to not attend particular status meeting.
In one of companys I did work, we had a woman, which was particularly good at moderating meetings - she was outside project. For a team, where people had issue with openly discuss problems and even cooperate well, she was introduced to help to talk. No strings attached, she was there to moderate, help execute the meetings, guide their way, no detailed reports provided up in the food chain. It was said at the day one. After two weeks communication in team appeared to change dramatically, and after one month this was completely another team - she helped them. The team needs to feel secure to openly discuss it's drawbacks.
I mean - I've seen a lot of retrospectives, even ones, where people where angry on each other and it got hot. I think it's crucial if you want to have SCRUM - one of cornerstones there is the team executing development, and the team is also about honest communication.
|
|
|
|
|
Michał Rybiński wrote: In SCRUM meetings, and particularly during retrospective after sprint, it is critical to ensure open, safe comm
And AGAIN, that is is the goal of all business meetings. And since SCRUM meetings are business meetings it applies to them as well.
Michał Rybiński wrote: I mean - I've seen a lot of retrospectives, even ones, where people where angry on each other and it got hot
And I have seen business meetings where that happened. I was at an interview for a employee candidate where employees started a heated discussion amongst themselves. At another requirements meeting a business analyst left in tears.
|
|
|
|
|
snorkie wrote: We're all friends here, and can discuss issues in front of everybody.
That's one of the three questions -> "Is anything blocking you?" If there isn't an issue then nothing is blocking you. Fixing the issue isn't part of the standup. Assigning the best people to get together to handle the issue after the stand-up is. The idea is to get a feeling on how well things are going and set up interventions when problems occur and don't pull the whole team into one person's problems. That issue should be resolved in the middle of the day or your backlog may be in trouble, which is another facet of the stand-up.
I think the stand-up is intended to make people want to leave and get on with their day. You can't sit back, close your eyes and drift in the boring meeting. (I have drifted off while standing up, but not in a sprint meeting, a meeting where everyone is required, not enough chairs, and well over an hour in the meeting with one guy monotone talking in front. I did catch myself before I fell.)
The idea is that everyone finds out that they know what they are supposed to do and when they leave the scrum, they should be either confident they will accomplish their goal or they will be getting the help they need to accomplish their goal.
Issue solving is a 2 to 3 person task, the whole team shouldn't be involved in it.
|
|
|
|
|
snorkie wrote: 1. Would any self organizing team of developers actually plan to meet every day?
Probably not, which is why you have to force them to do it.
snorkie wrote: 2. About half of the 15 minute morning morning consists of, "Lets have a Meet After to Discuss". Half the team stays after the meeting every day. How about just discussing it now and getting it over with?
That means that your sprint planning was not performed effectively.
If someone cannot simply say "This is the story I worked on yesterday, and this is whay I achieved", then look at fixing the sprint planning, not the stand-ups.
ALL planning and discussion should be completed in planning sessions. If it turns out that something requires further planning, take it out of the sprint, and get on with something that can be completed.
snorkie wrote: 3. The other half of our 15 minute morning meetings is just to state that the status hasn't changed from yesterday
If no stories have been advanced/finished since the day before, it had damned well better have been a Sunday, or you're all fired!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: If no stories have been advanced/finished since the day before, it had damned well better have been a Sunday, or you're all fired!
That's the usual result of a group just starting to do sprint planning. They haven't figured out how to create one hour or one day stories, so they never complete a story in one day, too much is in the story and they aren't breaking the stories up into small enough pieces. People hate going to sprint because they didn't finish anything. Realizing how to break things up small enough to always get something finished each day isn't yet in their mindset. They don't even know about poker card planning.
|
|
|
|
|
KP Lee wrote: They haven't figured out how to create one hour or one day stories, so they never complete a story in one day, too much is in the story and they aren't breaking the stories up into small enough pieces. People hate going to sprint because they didn't finish anything.
True.
This also means that they miss out on the satisfaction of actually finishing things, which is rare enough in the development game.
-- Closing a ticket because you've fixed a bug is pretty bleah.
-- Closing a ticket because you've finished part of a project, however small that part may be, is very satisfying.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I see where you're coming from I went through the same process of not trusting it when I started using scrum 6 to 7 years ago.
Nowadays my opinion has changed totally! I think it is a really effective way to develop software.
Developers and Testers, product managers are forced to talk, at first it feels really artificial and a waste of time, but after a few weeks you start to get really value out of the meetings.
The main thing you need to do is think differently, software is complex and although you write it, you are not the only person involved. You need to listen to feedback, you need to inform the others of your progress... the team becomes aware of the whole picture, not only technical issues with the piece of code you are writing, but you are also made aware of the nightmare your testers are going through setting up the right environment... etc... if you spend some time actually listening to the feedback you receive it will help you next time to write your code so that it facilitates the task of QA. And similarly if you let QA know that you struggled writing a piece of code they will take that into account and look at the result more carefully.
It took me some time to embrace Scrum and right now I think it is an outstanding way to develop. It teaches you humility when you listen, it encourages openness, it shorten the time needed to identify issues, it allows quick reaction to a customer who changes his mind. And above all it give everybody a voice... and that's good for productivity as it motivates people!
The team meeting in the morning is just on aspect of Scrum, this meeting will only be meaningful if the sprint has been planed carefully, if the stories are small enough so that you can actually say something about what you have done everyday. etc... If the meeting does not work maybe you need to review the sprint planning, was too much taken on? are the resource adequate? also mayeb the product backlog is not correct, you need short stories, you need priority etc..
Anyway that's my opinion. I think Scrum is really powerful and actually helps writing good software faster.
|
|
|
|
|
snorkie wrote: I've been doing SCRUM development for 4 weeks now and it feels like a huge waste
of time
I have never seen any research that suggested that any specific formal process control methodology provided a benefit over any other type.
I have seen research that shows that any formal process control methodology that is implemented effectively does in fact improve process flow in a number of ways. Of course if it is ineffective then it will do nothing but waste time.
|
|
|
|
|
jschell wrote: I have never seen any research that suggested that any specific formal process control methodology provided a benefit over any other type.
Even if you did, that would only prove the research was bad. No methodology can fix a bad team.
|
|
|
|
|
Nemanja Trifunovic wrote: Even if you did, that would only prove the research was bad. No methodology can
fix a bad team.
I don't see how those comments follow from what I posted.
Nor do I see how the first follows from the second presuming that is what you meant.
|
|
|
|
|
jschell wrote: I have never seen any research that suggested that any specific formal process control methodology provided a benefit over any other type.
The point is that if you are using a methodology, any methodology, badly, or not following it correctly, it will not work.
If scrum (or any other methodology) has been adopted by the OP's company, then discussions about whether or not they should follow it are immaterial. They have to do it right, or they're just wasting their time and risking their jobs.
Another point to note is that management will come gunning for anyone who intentionally does things to prevent it's working correctly, and will be right to do so -- you don't sabotage your home team.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: They have to do it right, or they're just wasting their time and risking their jobs.
It has been my experience that the vast majority of development shops fail to implement effective process methodology.
And effective doesn't mean that developers feel good but rather than the over all process such as delivery, overwork, bugs, features delivered, etc, improve once the process is put into place.
Mark_Wallace wrote: Another point to note is that management will come gunning for anyone who intentionally does things to prevent it's working correctly
Not any place that I have ever worked for nor that I have even heard of. At one company management terminated the formal process control because the company was acquired and the employees of the acquiring company found the process control confusing (and given that the code from the acquiring company was the worst code I have ever seen in my entire career it isn't a wonder that they were confused.)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
