ZenTao

 If you are reading this article, it’s quite likely that you are a programmer. Although programming is a noble calling, having some hobbies besides programming can bring great impact to your personal and professional life. I recently googled and found a survey at raywenderlich.com and here the results they found out the top 5 hobbies that programmers love! No. 5 Cooking According to raywenderlich.com, 28.1% of survey respondents chose cooking as a hobby. S paceX and Tesla CEO Elon Musk tweets often and generate a lot of speculation about future projects, or even...baking. ...

 Strong code ownership, weak code ownership and collective code ownership are the three main categories according to Martine Fowler , "Chief Scientist" of ThoughtWorks.  Strong code ownership breaks a codebase into modules and is assigned to one developer. Developers are only allowed to make changes to modules they own. Weak code ownership is modules that are assigned to owners but are allowed to be changed by other people. Collective code ownership abandons any notion of individual ownership of modules. The code base is owned by the entire team and anyone may make changes anywhere.  ...

  Scrum is one of popuar agile methodologies. It is a framework to manage projects, which provides specific procedures, specifications and principles to achieve the project goal. The quick way to understand Scrum is to understand the 3-5-3 structure.   3-5-3 Structure Simply put, the structure is 3 roles: Product Owner, Scrum Master and the Team. 5 events: Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospetive. 3 artifacts: Product Backlog, Sprint Backlog and Increment. If you want to know more about Scrum, you should read The Scrum Guide Daily Scrum, Review and Retrospective Meetings Scrum Poker: A Scrum Estimating Tool Kanban and Kanban tools 3-5-3 Structure in ZenTao Based on the philosophy of Scrum, ZenTao integrates bug management, test case management, CI and document management, and it completely covers the entire life cycle of software development. In ZenTao, the concepts of product, project and test are clearly defined. Product team, developi...

  ZenTao Open Source 12.5.stable is released.  This release is to fix bugs and to develop stories with top priorities. Changelog 5487 Add restrictions to the version number of ZenTao Pro and Ent.  5458 Date and HH/MM/SS should be recorded for Actual Start and Finish a task.  5389 Optimize the page for a successful installation. 5387 Admin-Develop-Entry. Remove extra coma for the alias.  5383 Add Convert to Task for Story.  5382 Add a prompt to Delete a project.  5261 Kanban. Drag a task to a swimlane and Assignee should be kept by default.  5221 Test-Request. Add Linked Library to search conditions for Link Case.  5219 Add Mailto in Doc.  5218 Add Todos by a specifi date.  5217 Add Tab and Query to Expect Versions.  5194 Task page. Click a story and create a case for it directly.  5193 Expect Case con is displayed in linked Request and Case Library.  5144 Admin-Custom. Add Read-Only control to Close Product/Project....

  As part of the Scrum community, ZenTao team joined the Scrum Guide 2020 Launch Meeting on Zoom. The closing thoughts from Dr. Jeff Sutherland are quite inclusive and were summarized below. Three major questions:  The new Scrum Guide says the Scrum Master is accountable for the Scrum team's effectiveness. In what ways do you see the Scrum Master doing this differently than in the past?   The Scrum Masters are now leaders who lead, instead of servant leaders. Is it indeed more than just a reordering of those specific words? What is the difference between a leader who serves and a servant leader?   The new Scrum Guide says the Scrum team is self-managing, but it was self-organizing. What does this change mean to us? Scrum Master and Team Effectiveness Jeff Sutherland  thinks the intent is the same as the past. But as Jeff and Ken were beginning to put this guide together, Ken said that the biggest problem in Scrum is the word "Servant Leadersh...

  A Burndown Chart is used to demonstrate the remaining work along with time. The workload is generally displayed on the vertical axis, and the time is generally displayed on the horizontal axis. It intuitively predicts when all work will be completed and is often used in agile software development, such as Scrum. Burndown charts can also be used for any project with measurable progress changes over time. The burndown chart above is a typical one and was made in ZenTao, a Scrum tool. It is the sum of the remaining hours of all tasks in the project. It is calculated every day to coordinate and the indicator lines are generated based on it. A Burndown Chart has four important elements: Horizontal axis: working days Vertical axis: remaining work Planned remaining work: a straight line Actual remaining work: a line goes up and down around the ideal line A Burndown Chart is to calculate the sum of the remaining hours of all tasks in the project daily (the blue points in the chart), and ...

Atlassian has just announced that the changes to their server and Data Center in October and they will discontinue selling server licenses. The policies for Jira Server Desk are as following, End of sale for new licenses On February 2, 2021, PT, we will stop selling new licenses for our server products and cease new feature development in our server product line. Three years of maintenance If you have an existing server license, you can continue to renew and receive maintenance and support for your licenses until February 2, 2024, PT. Updates to future pricing On February 2, 2021 PT, we will increase the price of maintenance for existing server licenses to ensure the continued security and maintenance of our server platform. Which means,  1. After February 2, 2021,  the server license  will  no more be on sale   anymore . 2. Maintenance costs will increase year by year. 3. For the customers who have already subscribed need to pay maintenance fees according to th...