Hi, Back to 2007, i was searching for an active Scrum community where i could propose a Scrum gathering in China, but i failed. Since then, ScrumChina yahoo...
Hi, all Here's another report posted on InfoQ China which is written by Steven Mak: http://www.infoq.com/cn/news/2008/10/learning-on-scrumchina-2008 BR -- ...
Hi all, in my company, some Scrum teams concerned that QA always felt very tight and tiered in Sprint. The reason was that QA could only start to test the code...
Yes, it's bad idea to have development sprint and QA sprint, and move back to single-functional team. This will delay your feedback, make your progress...
Agreed. In that way you won't be able to find and fix issue earlier also make the actual delivery duration longer. Actually without test, we really cannot...
... Normally this is the token of insufficient testing support. Either mentally or technically, e.g. feel QA is easy and fast to finish, do not take...
Thank you for all your suggestions. I want to give more clear situation about the issue. Basically DEV and QA will attend the planning meeting together. So...
... I am pretty sure that ATDD concept would help. The concept is always the same -- drive your development via having acceptance test cases first, while its...
... Recommend you to try this first, when I drive for this new way of working, I think this is will be a big problem. While using retrospective and 2-3...
About our gathering from Scrum Alliance website, http://www.scrumalliance.org/news_items/45 Also note this: The Scrum Alliance is considering hosting an...
Sorry, first of all, I do not agree on your title "DEV vs. QA ...", because they are not competing, but cooperating in the team. We had similar problem as your...
Hi, Ken presented some basic truths in Scrum. Basic truths about team motivation 1. People are most productive when they manage themselves; 2. People take...
... Nothing against XP, but I like FDD (Feature Driven Development). Simple, and a bit more evolutionary than revolutionary. Try as I might, I've never been...
We do Sit-together, one team one table, all sit together On site customer, PO is with team Continuous Integration Pair Programming, in most cases, we do pair...
Hi Vernon See inline comment ... Simple, and a bit more ... able to convince a single ... I don't think Pair Programming is very hard to adopt. In my personal ...
Hi For stories, we always use story point to estimate the size. However when you split one story to engineering tasks, what do you use to estimate, story point...
It's most common to use hours in sprint backlog and sprint burndown. Most teams i have worked with are updating remaining hours for tasks, while some teams...
... I also agree that learning TDD is hard. Any team has adopted TDD for most of the tasks? If yes, how did you make the transformation, e.g. did you hire TDD...
Hi Yi ... We are not there yet, still a long way to go. We are looking for both internal and external resources. I am not sure whether there is any good TDD...
... I didn't say Pair Programming was difficult to adopt -- I've found most developers open to, and if fact excited about the idea. I said it was difficult to...
... I like story points, both for product backlog and sprint backlog. Hours are linear, and everyone only has 24 per day (and hopefully aren't working all of...