ZenTao

  In this article, the rest of 19 key Agile terms will be introduced. Check another two articles, Agile Glossary 1st - Scrum, Kanban, and Extreme Programming (XP) Agile Glossary 2nd - Backlog, Iteration, and more Iteration Planning Iteration Velocity Kanban Board Release Planning Task Board Test-Driven Development User Story Workflow Work-in-Progress (WIP) Iteration Planning The goal of Iteration Planning is to define a set of user stories that will be developed in the next iteration. The customer should participate in Iteration Planning and provide a set of desired features. Developers break down user stories into tasks and provide estimates. The team signs up for several user stories (based on the previous Iteration Velocity) that will be completed in the next iteration. Iteration Velocity A summary effort of all completed user stories assigned to an iteration. For example, in Iteration 2 you have several user stories with the total effort of 50 points. All user stories were complete

  This time, we'll explain another 7 Agile terms that will help you decode this software development methodology. Agile Glossary 1st - Scrum, Kanban, and Extreme Programming (XP) Agile Glossary 3rd - Iteration Velocity, User Story and more Acceptance Testing Backlog Burn Down Chart Daily Meeting Effort Estimates in Abstract Units (Points) Impediment Iteration Acceptance Testing The functional testing of a user story by the software development team during the implementation phase. Usually the customer specifies scenarios to test when a user story has been correctly implemented. A user story is not considered complete until it has passed its acceptance tests. This means that new acceptance tests must be created each iteration or the development team will report zero progress. Backlog A list of user stories, bugs and features that need to be done. Product Backlog A list of customer requirements for the entire product. Release Backlog A list of user stories, features and bugs that sho

In this Agile glossary, we’ll explain 19 key Agile terms that will help you decode this software development methodology. Scrum Kanban Extreme Programming (XP) Acceptance Testing Backlog Burn Down Chart Daily Meeting Effort Estimates in Abstract Units (Points) Impediment Iteration Iteration Planning Iteration Velocity Kanban Board Release Planning Task Board Test-Driven Development User Story Workflow Work-in-Progress (WIP) image from proposalreflections.com 1. SCRUM Scrum is an agile methodology for software project management. Scrum was invented in 1993 by Jeff Sutherland, John Scumniotales and Jeff McKenna. According to latest surveys Scrum is the most popular agile project management methodology in software development. Often Scrum mixed with Extreme Programming engineering practices like TDD and refactoring for better results. Core Scrum practices are: Backlog (Product, Release, Sprint Backlog - lists of all functionality in product, release and sprint respectively) Iterative deve

  What is Waterfall methodology? The Waterfall Model methodology is also known as Liner Sequential Life Cycle Model. Waterfall Model followed in sequential order, and so the project development team only moves to the next phase of development or testing if the previous step completed successfully. What is Agile methodology? Agile methodology is a practice that helps continuous iteration of development and testing in the software development process. In this model, development and testing activities are concurrent, unlike the Waterfall model. This process allows for more communication between customers, developers, managers, and testers. https://hygger.io/blog/the-difference-between-agile-and-waterfall/ Waterfall vs Agile Key Difference Waterfall is a Liner Sequential Life Cycle Model whereas Agile is a continuous iteration of development and testing in the software development process. In Agile vs Waterfall difference, the Agile methodology is known for its flexibility whereas Waterfal

  When was the last time you ran into a challenge?  Right before you read this article? Thought so:) Maybe your developer just let you know they will need a full week’s work to fix a bug they just found, maybe you discovered that a month’s worth of timesheet time hasn't been filled out. Even if the challenge isn’t a strong enough word to describe the situation you find yourself in. Other project managers have been there before. We conducted a census from our zentao users about their experience, their projects, and the challenges they face. We got hundreds of responses which gave us some solid insights into the types of challenges pm’s face and which ones are the most common. We categorized the challenges and wound up with several different types. Here are the top three types of challenges. See where your biggest challenge is placed. 1. Coming in at number three, Personal Skills. If you are new to project management or you are thrown into the role head-first, you might wonder whethe

  Scrum tool selection criteria Every organization is different—a software developing agency can‘t use the same Scrum tools that a construction crew uses. However, there are certain elements that you certainly expect to see in any tool. There are some components for your evaluation below,  1. Product Backlog An organized backlog makes future planning and allocation of resources easy to manage. An effective sprint backlog should include ample storage and must enable prioritization of user stories. Changes in user stories and sprint backlog are also essential for the scrum tool. 2. Sprints This is the core of any Scrum tool. Sprints are repeated, predetermined periods of time for completing sets of tasks or work items from the backlog (generally from 1 to 4 weeks). Sprints should have connections with product or user stories, in each sprint, each team member should be clearly specified which backlog items or user stories should be done. 3. Burndown Charts These are graphical representati

In software development, an estimate consists of a quantified evaluation of the effort which is necessary to carry out a given development task.   What is meant by "Estimation"? In software development, an estimate consists of a quantified evaluation of the effort which is necessary to carry out a given development task. This is most often expressed in terms of duration. The intent here is to aggregate many individual estimates, so as to obtain an indication of the overall duration, effort or cost of a software project. Planning Poker is a consensus-based estimating technique.In Agile, it is used to estimate the product backlog: Story points Ideal days Any other estimating unit    that can be used with planning poker Estimate instances in ZenTao You could estimate product, sprint, story, task, test request, etc. when you are trying to create them in ZenTao. Some for specific hours, some for specific days or weeks. How to use planning poker for Agile estimation and planning? A

Collabora Online is a powerful LibreOffice-based online office that supports all major document, spreadsheet, and presentation file formats, which you can integrate into your own infrastructure. It's available to enable it in ZenTao easily. Step 1: Install Docker on Ubuntu For simplicity, this tutorial installs Docker from the default Ubuntu software repository. sudo apt update sudo apt install docker.io Once installed, the Docker daemon should be automatically started. You can check its status with: systemctl status docker Hint: If the above command doesn’t quit immediately, you can press the Q key to make it quit. If it’s not running, then start the daemon with this command: sudo systemctl start docker And enable autostart at boot time: sudo systemctl enable docker Step 2: Install and Run Collabora Online Server with Docker Execute the following command to pull the latest Collabora Online Development Edition image from Docker hub. sudo docker pull collabora/code Then start a new