Unit 14 – part 2 assignment – Final methodology comparison

19 May No Comments

Unit 14 – part 2 assignment – Final methodology comparison

Write a substantive 2000-word, Word Doc comparison of the three methodologies below using at least 3 tables with each table comparing the three methodologies in one or more domain.  Word count is in addition to words used in table. 

DAD – Disciplined Agile Delivery (new not covered in class)

SAFE – Scaled Agile Framework

Scrum – Class Notes, Lectures,

Include roles, processes, artifacts, benefits, complexity, usage, tools, and other domains you choose.

Also, write a 500-word description of which of the three would be most successful at your company and why.

Methodologies DISCIPLINED AGILE DELIVERY (DAD) SCALED AGILE FRAMEWORK (SAFE) SOFTWARE DEVEOLMENT (SCRUM)
Definitions DAD is practice of decisions framework that is used to enable a simplified process of the decisions that is around iterative and incremental solutions delivery. SAFE is known as a software development of agile framework. It is made up of a knowledge base of the integrated patterns that intends for the enterprise-scale of Lean-Agile development. SCRUM is incremental and iterative software development of agile framework for the management of the product development.
Roles Primary roles. Team member. It is led by the agile coach who is responsible for optimizing processes, ensuring availability or resources that are free from any obstacles and facilitating communication.Product owner. This is an individual who speaks as “one voice of the customer”. He is responsible for representing the stakeholders of the community needs to the team of the agile delivery.Architecture owner. This is the person who is responsible in facilitating the evolution and creation of the entire solution design and architecture the team’s decisions.Stakeholders. This is an individual who is impacted materially by the solution outcome. The person affected by the deployment and development of the software project.Team member. This is the person in the team that focuses on the production of the actual solution of the stakeholders. He or she is involved in programming, testing, designing, analyzing, estimating, and architecture and planning.Secondary RolesThis are the roles that are introduces to address the scaling issues. They include:Integrator. It is mostly used in building the whole system from its subsystems.Specialist. They are required sometimes depending on the project needs.Independent tester. Its role is to work parallel to validate the work.Domain expert. It is required mostly for the complex domains.Technical expert. Mostly brought up when a difficult issue is encountered. It includes agile database administrator, security experts, build masters and UX designers. The roles of the team here include:Responsibility of managing their own work.Committed continuously in finding different ways to improve.Estimating the complexity and size of the work.Responsible for building and value to continuously improve their deliverables quality.They are committed to the work they can finish in program increment or iteration time box.They are determined to the technical design within architectural guidelines. The Scrum Framework has three main roles that include:Product OwnerHe or she represents the customer voice and the products stakeholders. Their main role is to ensure the team members deliver value to the entire business. He or she writes the customer-centric items, add them to product backlog and prioritizes them according to their dependencies and vital. He or she also bridges the gap that exist between the stakeholders and the team.Development TeamThe role of the development team is to deliver potentially shippable increments of the product at every end of each of the Sprint.Scrum MasterThe role of the scrum master is to be accountable for the removal of the impediments to the team ability to deliver deliverables and product goals. The master also acts as a buffer between any distracting influences and the team. The master also ensures that the Scrum framework is being followed. The master also facilitates the team events, educates the stakeholders about the Scrum principles and promotes self-organization among the team.
Processes The processes of the Disciplined Agile provides a very light-weight guidance that assist a company to streamline information technology processes in a very context-sensitive manner. These processes include:The Delivery processesThis process is used to promote a working in the full, start –to-end and solution delivery lifecycle (scrum-based lifecycle, continuous delivery lifecycle, Kanban-based lifecycle and exploratory lifecycle). The process includes the concept, inception, construction, transition and production.For the process tailoring to support light-weight approach, Disciplined Agile framework must take the approach of a goal-driven. Its main objective is to guide individual through a process-related decision that they require so that scale agile and tailor strategies can be developed to addresses the situation they are facing.Information Technology (IT) Process. 2.0 Disciplined Agile framework is released so that it supports the full variety of the IT activities. Its process blades include disciplined agile delivery where the software teams usually follow the context-driven lifecycle that contain continuous delivery, exploratory, lean, and agile and program management. Disciplined DevOps that streamlined the IT operations and delivery that contains release management, operations, support and data management. Finally, Disciplined Agile IT, it is where all people involved in the IT eco-system work in a very learning-oriented, collaborative and evolutionary manner and it contains people management, product management, portfolio management, enterprise architecture, reuse engineering, IT governance and continuous improvement. The process of Scaled Agile framework includes the following:The Agile TransformationsThis is the first process that contains the Scaled Agile Transformation with a RAGE, Scaled Agile and Framework (SAFE) and Pilot Agile Transformation.Agile Hardware DevelopmentThis is the part of the process that includes the Agile Hardware Pilot and the Agile Hardware Training.Agile Implementation PhasesThis process includes the Agile Readiness Assessment, Agile Foundation Strategy Planning, Agile Mentoring and Coaching, Agile Coaching and Training, Change Management Services and the Agile Maintenance.Agile Training This is a process that contains the Public Training, Private Training and Online Training.Agile Transformation Case Studies Its process supports the work items so that it can track and plan the work, code review, feedback and test. It has five phases that explains the processes of SCRUM. They include:Initiate. This phase contains processes such as create project vision, identifying the stakeholders and Scrum Master, forming Scrum Team, developing Epics, creating the prioritized product Backlog and conducting the release planning.Plan and estimate. This phase contains processes such as creating user’s stories, estimating, approve and commit the user stories, creating tasks, estimating the tasks and creating the sprint backlog.Implement. This phase contains the processes such as creating deliverables, conducting the daily standup and groom the prioritized product backlog.Review and retrospect. This phase contains processes such as convening the Scrum of the Scrums, validating and demonstrating the sprint and retrospect the sprint. Release. This phase contains processes such as ship deliverables and retrospect project.
Artifacts The artifacts include: Acceptance TestBusiness RuleChange CaseClass Responsibility Collaborator (CRC) modelConstraintContract modelData Flow DiagramDomain ModelAbstract Use CaseEssential User Interface PrototypeFree-Form DiagramFlow ChartsGlossaryLogical Data ModelMind MapNetwork DiagramThe Object Role Model DiagramPersonasUML Activity DiagramUML Component DiagramUML Deployment Diagram Set of “SMART”. It includes the stretch objectives (described as the goals that are built for the plans but they are not committed by the entire team.Program board. They are used to highlight new features of the delivery dates, the dependencies that exist among the teams, relevant milestones and other ARTs.Vote of confidence or commitment that exist to the entire ART. Product. The mode of scum expects its team to bring system or product into a very shippable state at the Scrum Sprint end.Product backlog. This is a comprehensive document that is prepared by the owner of the product and it contains the list of the customer requirements that are prioritized by the business value.The Sprint Backlog. This is an exhaustive document that contains the information about the requirement that the team will implement and how they will be implemented by the team in the forthcoming Sprint.The Burndown Chart. It is a document that is used to show the collective work that remained in the Sprint and it is being updated in daily basis.
Benefits Decreases the time to the market. This is because it enables shorter change efforts from the automation.It decreases the cost to deploy. This is because of automated deployment, automated regression testing and management of the streamlined release.There is improvement mean time between the deployments. This is because of the continuous delivery and continuous integration that enables the teams to deploy regularized.There is improved quality. This is because the lean and agile strategies are used to apply on the data management that will improve the overall data of the quality across the organization.Improvement of the market competitiveness. This is due to improved quality.Improved decision-making. This is because of the real-time insight strategies from the operation intelligence. It is usually free and publicly available to be used.It is also highly available in an approachable and usable form.It is lightweight in its best sense.It is also practical. This is because its own targeted audience is individuals who do software development.It is specific. It is because it offers very specific practices, terms and concepts that are used by the software developers.It expediently codifies the common agile practices that are used today.Useful extensions are offered to the common agile practices.It also pounded the agile practices in enterprise contextIt is maintained regularlyIt also offers a very complete image of the software development. It provides better quality. This is because it helps in providing framework or the exposure and continual feedback so that it ensures high quality.It assists in decreasing the market time. This is because of the functionality is usually swarmed to the completion at each sprint.Assist the return on investment to increase. One of the reasons for this is that there is reduced cost of the failure.It provides a very high customer satisfactionBrings about a high team moraleIt increases ownership and collaborationIt provides metrics that are more relevantAssist in improvement of progress exposure and visibilityHelps in increasing project controlReduces risk by providing a constant feedback on the processes and products
Complexity It is usually viewed as being too complex and the technical complexity that the IT professionals may experience include:The new technology platformsThe multiple platforms of technologyThe legacy dataLegacy systemsCommercial off-the-shelf solutionsEmbedded solutions Its complexity mostly emotionally exists on the question whether the scaling agile approaches are adequate or not sufficient. Its complex is the unknown probe-sense-response to the emergent practices. Its demands courage, failures, fail-2-safe probes and learning. Its complexity looks at the cost of change. It considers the complexity of the codes. It is also relative to the knowledge and experience of an individual who applies the force on the object. They can easily understand the complexity of the knowledgeable and experience are equal in all team members.
Usage It is mostly used in cracking the solutions for all stakeholders.It is used in building the entire system from its subsystem. SAFE is used to agile development and scale lean in any big software company.It also used in providing assistant to the executives and team with consulting services, training and coaching. It is used to transform the project management across all business, industry and the life in general. For example, one can respond accurately and react quickly to the inevitable change.It is also uses by universities to deliver the valued projects to their clients.It is used by militaries to prepare the ships for the deployment.
Tools Its framework is very orthogonal to tools (the practices, techniques and principles that are captured by framework are independent of the specific tools) these tools include Microsoft TFS, Blueprint, enterprise transformation advisor, method park stages and rational method composer. The tools that are used to support SAFE depends on the levels. These tools include Plutocrat, scrum board, global roadmap and Kanban board Some of the tools that support SCRUM include Active Collab, agile for scrum, pivotal tracker, sprint ground, version one, agile agenda, agile bench, agile soup, agile buddy and more others.Spreadsheet. This tool is used to maintain and build the artifacts like the sprint Backlog.Proprietary and open-source software. This are the packages for the scrum.

Conclusion

The Disciplined Agile Deliver, Scaled Agile Framework and Scrum are all vital in one point and another. Organizations can adapt any of the three and implement in their own company. To me I believe Disciplined Agile Delivery (sets of practices that are advanced by the IBM so that it assists larger software teams of development to be more successful with the agile development as the smaller teams) will be more successful to my organization. This is because it assists in offering mix of framework that combines best direction from the variety of the proven and existing such as the crystals, Scrum, FDD, XP, AND DSDM agile practices. It will also assist the company in supplementing communal agile approaches with the firm’s guidance. For example, it assists the company team by showing them to develop and take the mainstream concept like the backlog to another level and make them to be more suitable to be used in larger organizations environments. Since the organization is large, it assists the company with project teams to get most out of the agile development methodologies. It also assists my company which is very large to deal with its large agile project in the complex company environments.

Disciplined Agile Delivery will also be more successful in my large company because of the company practically, it has four lifecycle that supports all the flavors of the agile while having some consistency that the framework provides, it has a lightweight, built-in agile governance, its development team are geographically dispersed, it also supports my company’s projects using traditional approaches by collaborating with the traditional teams. Dad is vital to my company since it supports the multiplicity of processes, technologies and people (more than 20) who are found within the large organization. In addition, DAD also provides a very relative advice regarding their trade-offs and the viable alternatives so that the company can address their issues. It also assists the company in adopting the strategies that a right and best for the organization. It also assists the company in delivery of the consumable solutions. It also creates supporting document for the company. The Disciplined Agile Delivery also provides a better foundation for the scaling. It also provides a flexible and rich guidance for vast array of the situation that the company faces. It usually does this through the process goal driven approach which is a very good choice for the company. (Mark, 2012).

Therefore, as a company, when we need to assemble the team for the DAD, we usually embrace the generalized specialists, creating team within the company that of the right size with the project, focus mainly on the collaboration of the team, better understanding of the company team and team principles and also try to be flexible and careful with the self-organizing teams. Hence the Discipline Agile Delivery is the best methodology that my company can adopt and make it more successful in the market because it is a very large company. In addition, will also advice most of the companies to adopt the DAD methodologies due to its numerous advantages and benefits and implement them especially the companies that are large.

References

Lines, Mark. (2012).” Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise”. ISBN 978-0132810135.

Heusser, Matthew. (2015).”Introducing the scaled agile framework”,  retrieved from CIO, pp. 1–2 — contains a review of the pros and cons of the methodology and concludes it is a half-way-house to a fully agile system.

Pichler, Roman. (2010). “Agile Product Management with Scrum: Creating Products that Customers Love”. Retrieved from Upper Saddle River, NJ: Addison-Wesley.




Click following link to download this document

Unit 14 – part 2 assignment – Final methodology comparison.docx