Is Extreme Programming only for the experienced? [

2019-03-16 14:21发布

I might be working with a team on a buisness workflow automation project, since it is a business workflow we are looking to have constant interaction with stakeholders and frequent releases. The team however, is pretty new and the average experience is around 3 years. Do you think the lack of experience could be a problem if the project was tackled in Extreme Programming way?? There doesnt seem enough Agile experience too. Would it be a good idea to let the developers talk to stakeholders or we need someone like a spokes person?

I would really appreciate your opinions on this.

14条回答
Deceive 欺骗
2楼-- · 2019-03-16 14:42

I'd invest in some training for the team with a scheduled "tune up" after they have been running awhile to keep them on course. Agile development and XP, in particular, requires discipline to make it work properly. There is no sense in learning bad habits that will come back to haunt you. Check out the training available from Industrial Logic, I've spoken with these folks at industry events and they really seem to know their stuff. I'm trying to find a way to get an enterprise-wide ability to use their training materials locally.

EDIT: I'm not too fussed about the 3 years experience thing. I'd be more concerned about them learning a new methodology. The techniques are not particularly hard, but doing them right takes practice. With no experienced person on the team and little experience with Agile, the time and money spent on getting some expert advice would be well worth your effort.

EDIT 2: As far as developers talking with customers. I agree with some of the others here in that I think you need a "go to" person that the customer can identify as the person to talk to unless your customer is part of the team. This person could be a team lead or an actual project manager. I do think developers need to be involved in direct discussions with the customer. Having the customer on the team is the best way to do this. If this isn't possible, then involve them in meetings, etc.

查看更多
萌系小妹纸
3楼-- · 2019-03-16 14:42

Extreme or not (I'd agree with others, that extreme programming should work in your case), but developers shouldn't talk with stakeholders on their own.

The flow of requirements and developer beliefs should be controlled. There should be some representative, so stakeholder won't need to ask 'whom should I ask if I want to know this?", and developers won't waste their time on doing things that are not discussed properly. There should be at least one person with some vision about what's currently being done and what are key features or problems.

EDIT: Developers should be aware of the discussions between stakeholders and teams representative, so they can react or respond if customer raises question, or propose some unusual/hard to implement feature.

查看更多
家丑人穷心不美
4楼-- · 2019-03-16 14:44

My experience with agile process is that it seems to work better with smaller teams working on smaller projects. Big teams and Big projects have trouble with achieving the quantity and quality of communication required for agile.

So the real question isn't so much how old your programmers are as it is how many you've got (and how many you think you need).

If you've got so many stakeholders and so many developers that you're thinking about providing a single point of contact, your project might be too big.

查看更多
放荡不羁爱自由
5楼-- · 2019-03-16 14:48

Seriously, I despise the term "Extreme Programming". It's asinine. Agile is good, the implications are mature, and the process works. I swear, Extreme Programming (grunt?) was proposed as a way to simply shake up the software development community. Agile development, and the Scrum methodology, would be my suggestion.

I think you probably just need to get a book on Scrum (try "Agile Project Management with Scrum") and that'll be a good way to go. Specifically, no, the devs don't particularly talk with stakeholders; that way lies madness. But there is, in Scrum, a Stakeholder representative who mediates the communication with the Stakeholder and servers as a gatekeeper for information in both ways. It's pretty well laid out in the book.

查看更多
混吃等死
6楼-- · 2019-03-16 14:50

I find that pair programming (and it's cousin pair debugging) is an excellent technique for sharing knowledge both between peers and people with different level of experience.

In my experience TDD is also suitable for less experienced developers.

查看更多
forever°为你锁心
7楼-- · 2019-03-16 14:51

That's how I learned C++ - with my only previous experience being BASIC on an old Tandy.

I think it's a great tool for beginners - both to a language, and to programming.

查看更多
登录 后发表回答