background preloader


Facebook Twitter

Priyanka Sheshadri

Nurturing Careers with specialized professional training services on Project Management related certifications

Workshops for Rich Agile Communication. In Agile “a workshop” is generally regarded as an activity where several people come together harnessing the interactions and creativity of the participants in order to achieve an objective.

Workshops for Rich Agile Communication

Typically, a workshop would last from 2 or 3 hours to a whole day. Workshops can be used at any point in a project whenever need arises. A typical workshop preparation requires to define: Workshop objective Why is the workshop taking place? Attendees Who should attend? Tools and techniques used and how they are used, play a significant part in successful workshops. Below are few of the Possible workshop techniques used: SWOT analysis Focuses on the four areas of strengths, weaknesses, opportunities and threats for a given situation. Gap analysis It is a three-step technique used to describe how something can get from one state or situation to another. Impact/effort grids Brainstorming Rich pictures Using visualization to convey messages (often feelings) in a form that can use metaphors and humour. Visioning. Rich Communication with PRINCE2® The most common problem faced by people working on projects is ‘Communication problem’.

Rich Communication with PRINCE2®

There are many communication problems that can occur on a project resulting in delays and mis-communication of information and mis-use of resources. There are various ways in which information and knowledge can pass between project stakeholders in the most effective way. This information flow needs to be managed effectively. Effective communication is very important to the Agile way of working. Communication can happen in many different ways as people interact differently during different situations. PRINCE2® identifies different communication channels as follows: World Of Agile +91-8291749529. For a PRINCE2 project it is recommended that Suitability of Agile is assessed throughout the project life (In agile terms mostly during retrospectives).

World Of Agile +91-8291749529

Most of the time the project situations are different affecting usage or working of Agile. Like the level of uncertainty involved or technology used or trust between the stakeholders. To assess the agile environment in order to tailor PRINCE2 in the most effective way to work with agile, PRINCE2 Agile guidance suggests using an assessment tool called “Agilometer”. Use of Agilometer helps you make an informed decision. The Agilometer looks at six key areas or categories indicating risk areas using agile. What to fix and what to flex for a PRINCE2 Agile project? Historically we have been discussing 3 major constraints of the project that needs to be monitored and controlled.

What to fix and what to flex for a PRINCE2 Agile project?

The term we used was “Triple Constraints” i.e. Difference Between PRINCE2® and PRINCE2 Agile® PRINCE2®, stands for Projects In a Controlled Environment.

Difference Between PRINCE2® and PRINCE2 Agile®

It is a very widely accepted project management methodology which was at first created as a UK government standard for IT projects. Later it’s popularity made it applicable across many industries. Now PRINCE2 is recognized as a generic project management method, suitable not just for IT projects but projects across all sectors, private as well as public sectors internationally (Mainly in the UK / Australia) PRINCE2® describes End to end method for project management. It suggests that you can control your projects, by dividing them into manageable stages and Managing One Stage at a time by Setting Tolerances for each Management Level in the Governance. Let’s look at the difference between PRINCE2® and PRINCE2® Agile certification. Prince2 Principles. What are the skills needed for Product Owner and Scrum Master? Skills of a Product OwnerChoosing the right product owner is crucial for any Scrum Project.

What are the skills needed for Product Owner and Scrum Master?

Following are some of the characteristics expected from the Product Owner· Visionary : Product owner should be able to envision the final product.· Doer : Product owner should also be a doer — that means, he should work with the team to get the final product ready.· Product Owner should be a Leader and Team Player· Communicator : The product owner must be an effective communicator and negotiator. The Product Owner is the Voice of the customer and therefore he should communicate customer needs and requirements and bridge the gap between the customer and the team. This may mean saying NO sometimes to the customer.· Empowered and Committed : The Product owner must have enough authority and the right level of management sponsorship to lead the development effort and to align to stakeholders.· Available and Qualified : The Product Owner must be available and qualified to do a great job.

ITIL General Management Practices. In ITIL, management practices are defined as “set of organizational resources designed for performing work or accomplishing an objective.”.

ITIL General Management Practices

These Management practices are the core or main component of Service Value System (SVS). In the Earlier ITIL versions the focus was on processes but with ITIL 4 there is more focus on practices and flexibility. The New ITIL® 4 practices are as follows: General Management Practices (14) – They have been adopted and adapted for service management from general business management domainsService Management Practices (17) They have been developed in service management and ITSM industriesTechnical Management Practices (3) They have been adapted from technology management domains for service management purposes by expanding or shifting their focus from technology solutions to IT services Here we try to explore General Management Practices adopted and adapted from general business management domains. By Priyanka Sheshadri. Over the years, Agile methodologies have taken the heat when they appear to have failed to deliver expected benefits to an organization.If our project fails, the tendency is that “we must blame the Agile process and our practices in some way for this”.Agile is not a magic stick to save a failing project and bring immediate results.

by Priyanka Sheshadri

It lets you uncover better ways of developing software by doing it and helping others do it.As with all development methods, the skill and experience of users determine the degree of success and/or abuse of such activity.So sometimes we obtain the agility by making up our own variation of this methodology. In this case, failure of this project should largely be incumbent upon us for deciding to sacrifice the practices we chose to ignore and the new ones we added. Some are Agile while just for namesake, and following no methodology, just cherry-picking a couple of practices here and there, and picking the principles they like.1. Myth about Scrum only being useful for Small Projects. It is a common mis-conception that Scrum is only useful for small projects.

Myth about Scrum only being useful for Small Projects

The real fact is that Scrum is used for solving complex problems. Complex problem is a problem where there are “unknowns” about requirements or the solution. For solving complex problems, the decisions have to be taken based on what has been done in the recent past. It is extremely difficult to base your decisions based on long-term assumptions. Myth about creating multiple Sprint Backlogs before first sprint starts. Common Misconceptions and negative implications Some teams treat the Sprint Backlog as just a smaller version of the bigger plan (Product Backlog) and start creating baselined Sprint Backlogs for multiple future Sprints.

Myth about creating multiple Sprint Backlogs before first sprint starts

The negative implication of this practice is that the “Inspect and Adapt” cannot happen. This becomes just disguising the waterfall and calling it Scrum. DevOps End of Service / Product Life. Agile Development Teams use DevOps to implement Continuous Integration and Continuous Delivery which helps them to launch their products at a faster rate into the market. The main reason DevOps is adopted are Predictability, Maintainability, Time to market, Quality Improvement and Resilience. The DevOps Lifecycle covers many important life cycle phases like Development, Testing, Integration, Deployment & Monitoring. But many times misses out on the End of product or service life. Here we try to Explore the ESOL in more detail. End of service or product Life a is the decision of many times taken by the Business Representative – either a Scrum Master or a Product Owner or a Sponsor. Myth about Sprint Planning consisting of Three Parts. Common Misconceptions and negative implications Most teams implement Sprint Planning as three parts – Part 1, Part 2 and Part 3.

The Product Owner comes in part 1 and 2, helps with setup of the Sprint Goal (WHY) selection of functionality (WHAT) and then the Developers sits and thinks over the technical (HOW) during the Part 2 of the sprint planning. The implication of this is that PO then does not get involved in the detailing and the road-blocks that team faces and technical feasibility problems that result during the Part 3 becomes a back-and-forth discussion between PO and Developers. Youtube. PRINCE2's Project Organisation. PRINCE2's organisation theme defines the Project Team or organisation. It establishes the project's structure of accountability and responsibilities. As PRINCE2 is based on a customer/supplier environment, it assumes that there will be a customer who will specify the desired result and probably pay for the project, and a supplier who will provide the resources and skills to deliver that result.

A successful project management team should have business, user and supplier stakeholder representation. Business The products of the project should meet a business need which will justify the investment in the project.Should also provide value for money.The Executive looks after business interests User The user viewpoint should represent those individuals or groups for whom some or all of the following will apply: Supplier The creation of the project’s outputs will need resources with certain skills. Scrum Guide 2020 - What's New? Excitement is in air. The new scrum guide is out. Like always there is a great curiosity among agile enthusiasts to see how the guide to scrum is evolving. This article attempts to capture this very aspect. Here, in this article I have articulated my understanding and perspective on how the guide has evolved in its latest avatar. Agile Administration in Tooling and Tool Integration. Tools are inherent to our jobs, inherent to how we solve the problems we face each day.

Our comfort level with the set of tools that are available to us, and our ability to adapt to new tools as they evolve and shape our thoughts and ideas. The availability of collective knowledge within the palm of your hand combined with the collaboration across organization and company boundaries through open source software is dramatically disrupting the status quo of work. Companies mired in managing infrastructure configuration management by hand with unknown numbers of divergent systems, unable to quickly change and respond to market demands will struggle against their counterparts who have managed to contain their complexity on one axis through infrastructure automation.

While it is possible to manage servers by hand, or even artisinally crafted shell scripts, a proper configuration management tool is invaluable especially as your environment and team changes. Website - Configuration Management in DevOps. What is ITIL? The term ITIL means "Information Technology Infrastructure Library". ITIL is the most popular and widely accepted approach to manage IT Service(ITSM).

ITIL has been adopted by many organizations as the framework to manage their IT service. There are millions of practitioners worldwide with ITIL skills and capabilities. IT is important to keep in mind that ITIL is a set of best practices and not a standard, so organizations are free to adopt ITIL framework as is applicable or valuable to them. Myth about Sprint Review being a sign-off event or a demo forum. Myth about baselining the Sprint Lengths at the start of the project. Common Misconceptions and negative implications Most organizations and Agile experts implement Sprint Length as a fixed length baselined at the time of writing a SoW or a contract.

Myth about Definition of Done being baselined before project starts. Common Misconceptions and negative implications. The Scrum Development Team. Myth about Scrum Master being a renamed Project Manager role. Common Misconceptions and negative implications Organizations implement Scrum Master role by renaming all their Project Managers as Scrum Masters just because they want to do Scrum or try Scrum.

Scrum Master is the most mis-understood role in the industry.Scrum Master remains the same “Command and Control” roleScrum Master is made accountable for Product Scope, Product Delivery, Product Quality, Product Budgets and Project Timelines. Management holds one neck and that is Scrum Master’s neckScrum Master becomes a coordinator as the Project Manager used to be. What is a User Story? - Welcome to World of Agile. The User Story is the most granular unit of requirement on a Scrum Project.

Kanban Boards or Task Boards - Welcome to World of Agile. Myth about Sprint Backlog being a commitment. Common Misconceptions and negative implications. Cumulative Flow Diagram - Welcome to World of Agile. Distributed Scrum Teams. Today businesses are shifting to emerging economies (such as India) due to reduced business operations cost and an easily available workforce. Myth about Daily Scrum being a status meeting. Utility and Warranty in ITIL4. Risk Boards - Welcome to World of Agile.

Information Radiators - Welcome to World of Agile. Story Point Estimation - Welcome to World of Agile. What is Kanban? - Welcome to World of Agile. Fascinating World of Agile. Agile Methodology and Frameworks - Fascinating World of Agile. Four Dimensions of Service Management in ITIL4. What is Agile Manifesto - Fascinating World Of AGile. Agile Project Management - Welcome to World of Agile. ITIL 7 Guiding Principles. Certified-Scrum-Master-Certified-Scrum-Product-Owner-CSM-CSPO-ACSM-India-USA - Welcome to World of Agile.

Amazon Elastic Compute Cloud (EC2) - Welcome to World of Agile. Amazon Elastic Block Store (EBS) - Welcome to World of Agile. What is AWS? - Welcome to World of Agile. What is PRINCE2®? - Welcome to World of Agile. Fascinating World Of Agile. Certified-Scrum-Master-Certified-Scrum-Product-Owner-CSM-CSPO-ACSM-India-USA - Welcome to World of Agile. Virtual Scrum Master Certification Online. Tracking Business Case in PRINCE2. Scrum Agile Interview Questions - Fascinating World of Agile. Agile and Scrum Quizzes - Fascinating World of Agile. Fascinating World of Agile. What is a Product? - Fascinating World of Agile. Story Point Estimation - Fascinating World of Agile. Choosing Right Pilot for Agile Implementation - Fascinating World of Agile.

Adjusting Master Contracts during Agile Transformations - Fascinating World of Agile. One-Team Culture - A first step to being Agile - Fascinating World of Agile. Agile Transformation Challenges. ITIL V4 certification Mumbai - Fascinating World of Agile +918291749529. Advanced Certified Scrum Master Training. Define Tangible Agile Transformation Items with concrete Business Value. Planning Agile Transformation Sprints - Fascinating World of Agile.

Running an Agile Transformation with an Improvement Backlog. Cucumber – Behavior Driven Development Tool for Automated Acceptance Testing - Fascinating World of Agile. World of Agile - Priyanka Sheshadri - Medium. What is Product Backlog and what does it content ? - Fascinating World of Agile. DevOps - Deployment Pipeline. Configuration Management in Agile Projects - World Of Agile. Tracking and Communicating Progress - Fascinating World of Agile. Scaling in DevOps. What is Risk as per PRINCE2 and How to Manage it? Steps for Transitioning to Agile - Fascinating World of Agile. Quality in Scrum. Project Charter and Visual Control in Scrum and DevOps projects. How Scaling works with Agile / Scrum? - Fascinating World of Agile. Top 5 Agile Certifications in 2019 - Fascinating World of Agile. Fascinating World of Agile. World Of Agile - Priyanka Sheshadri - Medium.

Why Automation is important for Effective DevOps - Fascinating World of Agile. CSM (Certified Scrum Master) and CSPO (Certified Scrum Product Owner) - Which is better for me? - World Of Agile. Product based Planning Technique in PRINCE2. Advanced Certified Scrum Master Training. What do you mean by Empirical Process Control in Agile (Scrum)? Who to Embed PRINCE2 in the Organisation. World Of Agile - Priyanka Sheshadri - Medium. Project Product Description and Product Description Difference Prince2? Best Practices of Continuous Integrations - World Of Agile - Quora. Scaling DevOps: - Priyanka Sheshadri - Medium. What are the different methodologies that can be used to manage an agile project? Risk Management in PRINCE2 - Priyanka Sheshadri - Medium.

Fascinating World Of Agile. Who is Product Owner in Scrum Team and what are the skills needed for a Scrum Product Owner? - Fascinating World of Agile. PRINCE2 Themes: - Fascinating World of Agile. Burn Up Chart - Fascinating World of Agile. DevOps and Software Development Process - Fascinating World of Agile. What are Important Roles in Scrum-Agile Teams? What is Definition of Done? What are the skills needed for Product Owner and Scrum Master? Distributed Scrum Teams.