Scrum with MS Visual Studio *2003* ?
- I've scanned this list and don't see anything about MS's plug in for
VS 2003, which turned up in a Google web search.
Yes, there's stuff for VS 2005, not an option yet. My client is
converting to 2005 but it will take a while and he'd really like to
integrate with his current version of VS. He is adverse to
spreadsheets. I'll start them off simple, but want to have this in my
back pocket (if worthwhile) in case their culture really can't live
with digital photos of whiteboards :-) especially since project
visibility is one major goal.
As often happens with SCRUM, the team needs to start immediately.
Can anyone tell me whether this thing is worth fooling around with?
What do I want to know?
- does it demand non-Agile data to work? (actuals, for example)
- is it stable?
- is it time consuming to install? to use?
PS: for use by a single normal-sized scrum team with a one member in
an offsite location. programming language is c++
- Steven Gordon wrote:
> On 2/7/06, David H. <dmalloc@...> wrote:I know :)
>> I do agree that people need to realise that most quality issues originate
>> higher up. Most of the time when the requirements are gathered.
> In Scrum, when are the requirements "gathered"? Who participates? It's not
> like a waterfall process where we can go blame some analyst.
But that is exactly my point. When all of the people refuse to work together,
customer, business unit, analysis, the quality of the product will suffer.
Often enough some software department has to deal with developing software for
a domain they know nothing about. Yet there is no insider they are allowed to
talk to. Now what will that do to Quality ?
> It would be a process smell if the team depended on the QA person to ask theActually I was more thinking that the QA person is there to kick off the
> difficult questions while all the developers just sat there daydreaming
> about how they were going to code it.
important act of questioning yourself. I do look at this from a more
philosophical point of view than a technical one. Everyone can be the QA
person in a team and I hope that all of us have a QA person in us. I know that
I do QA aspects whenever I am Scrum Master for a project. However it helps
when someone steps up and states. "Yepp I will have an eye on it, maybe more
so than others"
> If the developers cannot ask the right questions, the solution is not toYes, see above, I do believe we agree here.
> depend on somebody else to ask them, but to integrate somebody into the
> team who can show them how.
> Integrating that person into the team wouldOnce more, yes, yes, yes :)
> mean they do not do all the QA work and they do not just do QA work. If you
> do not integrate that person, then the cross-training will be much less