“Plan your work, then work your Plan” by Martin
Fowler and Neal Ford
There are many traditional approaches to software
development, one of it is waterfall development which follows up the sequential
steps/process /phases, in which one phase of the project must be completed
before the next phase can begin example water fall model, just like automobile
on an assembly line.
So here one rarely re-visit
phase once its completed , that means you better get whatever you are
doing right the first time. You don’t realize any value until the end of the project,
leave testing until the end, this approach is highly risky, often more costly
and generally less efficient than Agile.Here in Agile we follow the recursion of all the phases in multiple sprint.
Agile Manifesto
- Work closely with client, in all the phases of development cycle
- Welcome changing requirements, even late in development.
- Business people and developers must work together daily throughout the project.
- At regular intervals, require complete team involvement, by this we achieve technical excellence and come up with good design and approaches.
How it works
- Split your organization into small cross-functional, self-organizing teams. [Project owner/ Scrum master /Scrum Team]
- Split work in to a list of small concrete deliverable. Split time into short fixed- length iteration/ sprints
- Optimize release plan / Optimize the process.
Things we do in scrum
Describe the user story – Estimate the work associated –
Rank them in order of importance – Daily scrum meeting to discuss what did you
do today? What you will do today ? Any obstacles?
Agile Success
Ref:
Hello, I really liked the quote at the top of your post. I also like how you talked about other methods of development in your introduction. I think you are better than most with using conversational tone, grammar, and overall quality of what you write. I like the design of your QR code as well, but wasn’t able to scan it. (Maybe its my scan app, camera, or screen). I think you did a good job, keep up the good work.
ReplyDeleteHi Vimal. Your points about Agile being all about the user story is an angle I had never really taken the time to consider before. When you think about it, the end-user will be the one using that software permanently (well, you'd hope anyway ;). In order to ensure that goal, it's imperative that your team and product manager work to keep the software improving at a consistent pace. That way it'll keep making a positive impact on the customer or user.
ReplyDeleteI really like how your post describes the whole process of an Agile developed product. Isn't it weird to think that are companies out there who still use an assembly line method in their production process? I think so and I am sure from reading your post you would agree as well. That being said, here is some constructed criticism. When presenting your overview of Agile development you never considered that an alternative to Agile may actually be better. Of course, I even said above that it's crazy not to use Agile, but I still considered companies who do create a successful product without this model. Minor semantics, but addressing the opposite of your point of view is just a more objective way of presenting an idea. Overall it was a great post that clearly mapped out everything in Agile nicely, just didn't consider an alternative.
ReplyDelete