Agile Methodology of Michael Chiozza Samples †MyAssignmenthelp.com

Question: Discuss about the Agile Methodology of Michael Chiozza. Answer: Introduction The case study that is given is about a company whose chairman Michael Chiozza works in the power generation, mining sector and information technology. The executive staff of the company fails to implement the project methodology that helps to increase the market influence of the company. Michael Chiozza has ordered to implement a Project Methodology that increase the market influence of the company. The suggested method that the company should follow is the Agile Methodology. The presentation describes different aspects of Agile Method which helps to benefit the company of Michael Chiozza. Agile Methodology The alternativeproject management software development methodology that can be used by the chairman Michael Chiozza is the Agile Methodology. Agile is a project development method that should be used by the company of Michael Chiozza to establish in the market (Al-Azawi, Ayesh and Obaidy 2014). A group of methodologies of software development that is related with iterative development is the agile method of software development. The method of agile software development helps to discipline the process ofproject management which enhances frequent adaptation and inspection. It also enhances a teamwork that has a leadership philosophy, self accountability and organization and also comprises of a set of best practices of engineering which results in high quality software. Agile methodology is a process of development which relates with the goals of the company and satisfies the need of the customer. The concepts that re related to Agile Manifesto is the development of agile methodology. Life Cycle of Agile Method Initiation: The initiation method describes the strategy that is behind execution of the project. Development Phase: In this phase planning should be done about how to increase the market influence of the company. The details of the breakdown of the strategies of process that is followed by the company should be detailed and all the risks that are associated with the planning process are to be developed. Acceptance Phase: In this phase the project is accepted if all the planning and development phase methods are accepted. If not, then changes are implemented accordingly and then it is deployed to the customers. Iteration Phase: As Agile method is an iteration process, the full process is repeated once more for further confirmation. Strategies for Continuing Professional Development (CPD) The development of all the knowledge that are needed in software development and the technical personal, professional, skills that are related to business and management throughout the life cycle of the project is known Continuing Professional Development. The strategies of Continuing Professional Development are applied to all the workforce of social care all over the setting of organizations. All the workers and the managers are applied in the Continuing Professional Development which also includes the social workers that consists of learning of all types at all the levels of software development (Patwardhan et al. 2016). The strategies of Continuing Professional Development include qualification, registration, post registration and training. The strategy of Continuing Professional Development reflects model of social development that helps to promote and give value in greater recognition for all the work that is done and also the roles that comes under social care that are paid an d non paid and also enables flexible pathways for career. Agile Practices that are followed The practices that are followed by the agile methodology in developing a software development are as follows (Iqbal and Javed 2014): Development of test driven programming, Refactoring that is rigorous and regular, Integration that is continuous, Simple design of development, Programming pair, The codebase is shared in all the programmers, A single standard of coding is adhered by the programmers, A single war room is shared among all the areas of agile methodology. Agile framework There are many frameworks that the agile methodology works with. These are as follows: Scrum Agile Methodology The method of Scrum Agile is based on the interaction between three main roles that are systematic: Scrum master, Team and Product Owner (Al-Azawi, Ayesh and Obaidy 2014). The Scrum Master is a figure that is central within a project. This helps to eliminate all boundaries that obstruct the efficient working of the team. The Team of Scrum is a group of self organizing and cross functional people who are responsible for the implementation of the product. A scrum team should have at least seven team members so that they can stay flexible and also productive. The work of project owner is to be involved throughout the project which conveys a global vision of product. This product is usually a stakeholder or a customer. The project owner conveys a vision that is global throughout the project and provides feedback after completion of the job. The artifacts that Scrum depends on are manages all the requirements and also tracks the progress that includes products backlog, chart of sprint bur ndown and sprint backlog. Kanban Framework The framework of Kanban is to prioritize work that is in progress. The Kanban method limits the scope so that the team matches the capacity effectively. When the task gets completed, the team of the Kanban takes the work that comes next in the pipeline (Butt et al. 2017). The development process gives more planning flexibility, clears the objective and also provides a transparency of the work that is being done. Lean Agile Framework: Eliminating all the waste that comes in Software Engineering This method of Agile is the thirdly most used approach agile method. Near about 21% of the organization possesses the Lean framework. This method is an incremental and iterative methodology. Seven basic principles are included in Lean Agile framework: Eliminate waste Create knowledge and Amplify learning Decision is taken lately Deliver is very fast Empower the full team Build integrity or quality in project development See all the process as a whole. Responsibilities in Agile Methodology Product Manager orProduct Owner: The Product Manager orProduct Owner is the CEO of product that is being made. The Manager focuses on the long term product vision and short term product vision in a product line (Peroni 2016). They also represent the interest of customer. They represent the product in the outside world. RESPONSIBILITIES: Responsible for the markets, competitive analysis and business case, Responsible for short term and long term product vision, Responsible for Net Profit and ROI, Features are prioritizes for releases that are based on expected ROI, Writes the Acceptance Criteria, User stories are written, Tradeoff decisions are made between scope that is value that is expected in ROI and also the schedule. Program Manager: The Program Manger solves the problem and also makes decisions that are impartial which is not biased to the product or to engineering or to any different groups (Borad et al. 2015). RESPONSIBILITIES: Planning process is managed, Program schedule is managed overall, Drives multiple projects or releases, Facilitates Release of Retrospective and Planning, Access to people and tools are provided, All action items for project are owned until right owner is found, Reporting the project status in all directions is owned, Coordinates other supports that are release, Responsible for mitigation and risk assessment, Educates or Enforces that is agreed on methodology and processes rules, Educates or Enforces responsibilities and roles. Architect: The Architects are those who lead the direction that are technical in the method of agile methodology. RESPONSIBILITIES: Responsible for systems of cross functional that is designed from end to end and are also needed for communication (Tavakoli, Gandomani and Ahmadi 2016). Works with Project Manager to group the features that is based on Architectural Elements that support them on priorities, Tests the Architectural Elements with testable and executable design that includes abstract interfaces. Facilitates the technical decision, incorporates feedback and emergent patterns from team back into overall design, produces detailed approach and alternate the Design Concepts. Ensures all the Design goals including Accessibility, Modularity, Reusability, Reliability, Performance, Maintainability and Internationalization, Technical cohesion is ensured and technical contract is written in the interfaces and other objects that are and data entities, Leads provides feedback and design review. Engineering Manager: The work of Engineering Manager is to ensure the completion of work that is in progress successfully and also understands process in which product is created (Dhir and Sarraf 2016). RESPONSIBILITIES: Responsible for lead time and production rate, Responsible for initial sizing that is of high level, Works with team and architect to prove the technical integrity, Responsible to conduct investigations on technology of forward leaning (spikes), Negotiates with architect that depends on the technical approaches, Most bottlenecks are removed, Engineering of best practices are enforced, Motivation of the team is ensured, Team members career development is assisted. Product Developer: The Product Developer is used to create the product RESPONSIBILITIES: Sizes of all backlog items are estimated, Translation of all backlog items to logical units of task and engineering design, Technical feasibility is evaluated, Backlog items are implemented, Writes and also verifies the code that adheres to acceptance criteria, Application of best practices of product development. Quality Assurance: The Quality Assurance prevents defects that enter the system instead of finding them at last (Duka 2013). This also facilitates the building integrity of the software development process and the product. RESPONSIBILITIES: Test plans are written by QA that enforce features acceptance criteria, Keeps test plans and cases that are updated for changing requirements, Continually integrates base of the code with tests regression at functional level and builds automatically, Notifies when there is blockage in the production that happens due to errors of development, Measuring Quality, Defining Quality, Improving Quality and Quality Assurance Best Practices are enforced. References Al-Azawi, R., Ayesh, A. and Obaidy, M.A., 2014, January. Towards agent-based agile approach for game development methodology. InComputer Applications and Information Systems (WCCAIS), 2014 World Congress on(pp. 1-6). IEEE. Borad, A., Rajput, I., Borad, A. and Rajput, I.J., 2015. Software Engineering-Agile Methodology using Butt, F.L., Bhatti, S.N., Sarwar, S., Jadi, A.M. and Saboor, A., 2017. Optimized Order of Software Testing Techniques in Agile ProcessA Systematic Approach.International Journal of Advanced Computer Science and Applications (ijacsa),8(1). Development: A Case Study of XP Agile Methodology.International Journal of Software Engineering and Technology,2(1). Dhir, S. and Sarraf, S., 2016. Crime and criminal tracking networks systems using agile methodology.BIJIT-BVICAMs International Journal of Information Technology,8(1), pp.930-933. Duka, D., 2013, May. Adoption of agile methodology in software development. InInformation Communication Technology Electronics Microelectronics (MIPRO), 2013 36th International Convention on(pp. 426-430). IEEE. Iqbal, U. and Javed, A., 2014. Scrum (R-Scrum) Introduction Of Model Driven Architecture (MDA) In Agile Methodology.International Journal of Scientific Technology Research,3(11), pp.296-302. Patwardhan, A., Kidd, J., Urena, T. and Rajgopalan, A., 2016. Embracing Agile methodology during DevOps Developer Internship Program.arXiv preprint arXiv:1607.01893. Peroni, S., 2016. SAMOD: an agile methodology for the development of ontologies. SCRUM.International Journal for Innovative Research in Science Technology,1(12), pp.175-189. Singh, S., Kumar, N. and Bansai, V., 2015. Adoption of agile methodology in software industry.International Journal of Scientific Engineering Research,6(5), pp.198-142. Tavakoli, Z., Gandomani, T.J. and Ahmadi, M., 2016. Knowledge Management in Agile Software