Implementing Scrum helps your development department but breaks the old way of doing things, so the overall process actually slows down. Everyone was bashing your development department. You were too slow, you were the bottleneck – if only development would be faster, we could earn so much more money … you know what I’m talking [...]
Scrum – Iterative, incremental methodology for project management
An agile based practice of software development favors short iterations and rapid releases. Agile software developers love them some Scrum!
Imagine you’re driving your car through uncharted territory to a destination only vaguely described by “That Guy” who told you to go there. “That Guy” was kind enough to give you an absolutely non-negotiable deadline too. With that in mind, you race to the first waypoint – you should already be able to see it [...]
It’s amazing. Talking to a bunch of fellow CTOs I heard a lot of them saying: “We introduced Scrum and it works really well” and “we’re too slow to bring new features to our customers”. This piqued my curiosity. Scrum is supposed to speed up feature delivery through short iterations. How can an organization claim [...]
In Scrum, sprints are time-boxed delivery cycles that help keep the team focused on the goal. If you don’t know which goal I’m referring to, check out Dr. Eliyahu M. Goldratt’s novel “The Goal” (hint: I think it’s something about making money). For web development, I run weekly sprints and this surprises a lot of [...]
One of the most challenging things about introducing Agile in the workplace is that it’s not very widespread. People have heard mixed reviews about it’s implementations, and are hesitant to exchange the known (no matter how bad it may be), for the unknown. More and more companies, however, are adopting Scrum for their project management. [...]
Scrum defines a set of required meetings: Sprint Planning, Daily Scrum, Scrum Review, and Scrum Retrospective. Additionally, there might be a Scrum of Scrums, if you’re running multiple Scrum teams in parallel. If you’re doing two week sprints you spend at least half-a-day per week in Scrum meetings. Isn’t that a lot of additional overhead?
This is a guest post by Boris Gloger (@borisgloger) A couple of days ago I commented on Matthias’ post about the myth that Scrum forces a team to release new functionality only after a sprint is finished while Kanban would is more flexible. I wanted to know the difference between Scrum and Kanban, and why [...]
In the heat of introducing agile practices like daily stand-up meetings, retrospectives, unit testing, or defining “Done”, you can get easily overwhelmed by all the new and shiny ideas. It’s a real danger that implementing these new practices creates huge overheads, slows you down, and frustrates the team. They forget why you actually introduced agile [...]
Product development needs consistency The basic idea of Scrum is to create a safe and change-free environment to enable a team to concentrate on the planned development tasks. The team plans out a sprint of typically two weeks and the idea is that they work uninterrupted during this period. This process really helps to get [...]
The company my team is delivering additive value to product in terms of continuous evolution there are two principles which makes me think more about release cycles. The company PO conducts Integration Testing and when it has passed they conduct User Acceptance testing. Without those procedures they are not releasing the release into production. User [...]