Scrum got specific ways for testing software?
When reading Scrum Guide, as the official text for scrum, I find out there is no specific solution to provide software testing in scrum. (the only hint is on page15)
What to do when a sprint is finished early?
What to do when a sprint is finished early?
Why does the Scrum guide say no testers?
I have been reading the Scrum Guide from scrum.org and it says:
How to implement Scrum in a company with three similar web-based products
I am somewhat familiar with the concepts and benefits of Scrum. With that in mind, I am trying to improve the failing Scrum product management structure of a company I’m now working for that has three separate B2C products, catering to the same demographic and accessible on the same website. Each product has a product owner and a unique development team (5 – 9 people in each) behind it.
Handling unexpected features during sprint
Our team is going to adopt scrum and agile technics. We’ve got a product, which we develop for multiple customers. This customers supplied us with necessary requirements, so everithing is fine to adopt agile techinics.
Why do we use story points instead of man days when estimating user stories?
In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories are measured in Story points. Story points are used to calculate how many user stories a team can take in an iteration.
How should we draw the release burndown chart?
I have been in various Agile projects and seen many release burndown chart styles. Most of them were handled manually since somehow all the tools that I have run across don’t produce really useful burndown charts.
How can I plan optimization tasks in Scrum?
Recently my Scrum team has received several requests for optimizing certain parts of our code. Looking at the software with a profiler found some spots where the code could be improved.
Velocity does not plateau over time, why?
I have plotted my team burn up chart and its velocity per iteration. To me it looks really bad (velocity fluctuates a lot). What should I be looking for to diagnose the root cause of this behaviour?
Distributed SCRUM team issues: The work environment
One interesting issue appeared for me today. In a distributed SCRUM team when do you start enforcing an unitary work environment in terms of code format, IDE plugins (checkstyle & co), VCS, CI? The team is in an exploratory phase and thegoal is not production quality code but rather proof-of-concept. Isn’t it an overhead to enforce some common coding rules “a priori” – before the team members decide which are really relevant for their future work? Using this kind of tools is for sure a huge benefit because they act as an heuristic to minimize the technical debt but enforcing rules as “no trailng spaces” that really break the Jenkins build seems for me an overkill for a phase that should be focused rather on ice-beaking than on creating production code.