Today, better and better approaches were applied in application development; one of these is the agile method, yet, in order to encourage project success, adopting with PMBOK guidelines can make it concretized. By definition, agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals.[1]
One example commonly used with agile software development is the scrum, by definition, is an iterative incremental framework for managing complex work. The question now is does this method map out the PMBOK guideline, a guide which is an internationally recognized standard that provides the fundamentals of project management?
As to discuss, we state some important scrum fields that fit the PMBOK way such as, project is split into sprints same application from the latter where project is split into various phases, one after the other(PMBOK). Planned project is planned sprints in scrum, project planning will be done in the beginning of the project while planning will be done at the initiation of the sprint only for that sprint.
Scrum is an agile process for software development. In scrum, there is a series of jobs to be done called as sprints. Typically, each sprints ranges from two to three weeks. Scrum is usually made up of five to nine people and these people work hand in hand with each other in making the project. Unlike the traditional process development, scrum does not follow traditional division of tasks. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint. At the end of each sprint, Scrum fundamentals roles, namely, product owner, ScrumMaster and team member. Each of these roles constitutes to the success of the project development.[2]
Power of scrum:
Dangers of Scrum:
In scrum, the product owner represents the customer’s interests, responsible for communicating the vision of the product development and most importantly, he is the one with the most responsibility.[2]
The ScrumMaster is the one responsible for organizing the team. He or she must make the team productive as possible. Also, the ScrumMaster serves as a communication gateway for the product owner and team members.[2]
The team member is responsible for completing the work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers.[2]
What’s good in scrum is that at the end of each sprint, stakeholders and team members meet to assess the progress of a project and plan its next steps. This allows a project’s direction to be adjusted or reoriented based on completed work, not speculation or predictions. A basic principle for scrum is INSPECT and ADAPT.
References:
1. http://en.wikipedia.org/wiki/Agile_software_development.Retrieved.29Nov09.
2.http://www.mountaingoatsoftware.com/scrum.Retrieved.29Nov09.
One example commonly used with agile software development is the scrum, by definition, is an iterative incremental framework for managing complex work. The question now is does this method map out the PMBOK guideline, a guide which is an internationally recognized standard that provides the fundamentals of project management?
As to discuss, we state some important scrum fields that fit the PMBOK way such as, project is split into sprints same application from the latter where project is split into various phases, one after the other(PMBOK). Planned project is planned sprints in scrum, project planning will be done in the beginning of the project while planning will be done at the initiation of the sprint only for that sprint.
Scrum is an agile process for software development. In scrum, there is a series of jobs to be done called as sprints. Typically, each sprints ranges from two to three weeks. Scrum is usually made up of five to nine people and these people work hand in hand with each other in making the project. Unlike the traditional process development, scrum does not follow traditional division of tasks. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint. At the end of each sprint, Scrum fundamentals roles, namely, product owner, ScrumMaster and team member. Each of these roles constitutes to the success of the project development.[2]
Power of scrum:
- More business value delivered sooner
- Better return on investment for projects
- visibility to team and customers is greater
- producing of products increases
Dangers of Scrum:
- it is difficult
- it demands highly on honesty and transparency
- Bad products will be delivered faster and doomed projects will fail faster
In scrum, the product owner represents the customer’s interests, responsible for communicating the vision of the product development and most importantly, he is the one with the most responsibility.[2]
The ScrumMaster is the one responsible for organizing the team. He or she must make the team productive as possible. Also, the ScrumMaster serves as a communication gateway for the product owner and team members.[2]
The team member is responsible for completing the work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers.[2]
What’s good in scrum is that at the end of each sprint, stakeholders and team members meet to assess the progress of a project and plan its next steps. This allows a project’s direction to be adjusted or reoriented based on completed work, not speculation or predictions. A basic principle for scrum is INSPECT and ADAPT.
References:
1. http://en.wikipedia.org/wiki/Agile_software_development.Retrieved.29Nov09.
2.http://www.mountaingoatsoftware.com/scrum.Retrieved.29Nov09.
No comments:
Post a Comment