Browse DevX
Sign up for e-mail newsletters from DevX


eXtreme .NET: Practice Your XP with a Fictional Case Study : Page 2

Here's a perfect chance to be the proverbial 'fly on the wall' as you listen in on a team's efforts to use XP (eXtreme Programming) techniques to improve the way they deliver software.




Building the Right Environment to Support AI, Machine Learning and Deep Learning

Team Meeting
Customer Chris: Hi, everyone; how are you doing? Team: Hey, Chris.

eXtreme Eddie: I think we're doing pretty well; we finished the last few tasks on the project yesterday and we are waiting for feedback on that now. Panic Pete: (Laughs nervously.) Yah, I hope it's ok. I didn't do much work on that project and I'd be stuck if I have to do any maintenance on it.

.NET Deepak: Relax Pete, I know most of it quite well. I can help you. Panic Pete: (Sounding a bit relieved.) Thanks man. So what's next? Is there a new project for us, Chris, or can we kick back for a few weeks?

Pete grins a wide cheesy smile to the whole team, knowing full well that Chris has got a new project lined up for them. Skeptic Sue: Hey Pete, get with the program, this is serious. You know we've got the contract to develop a solution for SportSPeak.

.NET Deepak: Cool. Aren't they the life coaching and training company? Customer Chris: Yes, they do a lot of things: outdoor adventure training, motivational training, personal life coaching.

eXtreme Eddie: So what do they want? Just a Web site? Customer Chris: Well, sort of. They have grand plans for content delivery and also some smart client applications for their customers. I am meeting them tomorrow to discuss priorities and work out the best way to deliver the iterations to them.

Panic Pete: So what exactly is the point of this meeting? Pete casts another grin around the room, to which Sue responds with a hard stare.

eXtreme Eddie: Ok guys, enough already! Customer Chris: I want to make sure you are ready to start work on this project in a few days when I can sit down with you and go through the requirements.

.NET Deepak: Oh, so we have some time to kick back? Deepak winks at Pete. Sue puts her face in her hands.

eXtreme Eddie: Actually we do have something to do in the next couple of days. We're at what is known as iteration zero. We can get our development environment set up, and make sure we are fully prepared to start work on the first iteration of the new project. Panic Pete: I've already got Visual Studio .NET installed. What else do we need?

eXtreme Eddie: Well, what about a source code control system, automated build scripts, the build machine, task tracking, and all that stuff? Panic Pete: (Sounding stressed.) Panic! We haven't had to do this before.

Skeptic Sue: I think what Eddie suggests makes some sense! We can get it all set up so we are ready to get started as soon as Chris has worked out all the requirements with the customer. Oh, and don't forget we'll need a bug database. Panic Pete: (Sounding stressed.) Again, this is different than before.

Customer Chris: Sorry, did you say bug database? What do you need that for? Are you planning to write bugs? Skeptic Sue: Of course we won't try to write bugs Chris, but they will occur and we'll need somewhere to record them and their solutions.

eXtreme Eddie: Actually I'm not sure if we will need a bug database yet; it depends on the scale of this project. I'd like not to have somewhere bugs can hide and be hidden. Bug databases can be abused. We should aim to fix bugs as soon as they discovered so we can move forward and deliver a zero defect solution. Panic Pete: (Sounding more interested.) Cool, I've never written a zero defect solution before. Does that mean totally bug free?

eXtreme Eddie: It means it has no known defects or bugs. I believe it is possible to write bug free code if we don't let the bugs multiply. .NET Deepak: Sounds ideal.

Skeptic Sue: Um... sounds a bit too ideal. But if Eddie thinks it can be done then I'll give it a go. If we get to a point where there are more bugs than we can fix, then we'll need a bug database. Customer Chris: If you get to that point, you might not need a bug database! (grins) OK, I've got another meeting to go to, so I'll see you all soon.

eXtreme Eddie: Ok, I'd like to look at setting up a third-party tool I've been exploring called Cruise Control to do automated builds and provide us with feedback as to the state of the build. Skeptic Sue: Can I pair program with you on this? I've never used Cruise Control before.

eXtreme Eddie: Sure, let's do it.

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date