versionone kanban

Sixth chapter-Agile processesThe sixth chapter introduces the agile process in detail, in the Software engineering category, "Agile process" is a set of values and methodologies. This chapter is based on the scrum methodology of agile processes, and the essence of agile processes is rapid delivery. The process of agile development is as follows:1. Find out what needs to be done-product Backlog.2. Decide what the current sprint needs to solve--sprint Backlog.3. Sprint (Sprint). In the sprint phas

developers, SQA, product personnel, operation and maintenance personnel exchange.Instantiation requirements: How the team delivers the right software: Each tester deserves a read (should be recommended for all members of the team), and you will definitely be bright and say: Great! That's the way to do it! The highest state of the book is an ideal "live Document System", in fact it is difficult to fully achieve, but in the inside of each part of the implementation of the test will improve the ef

Daily Standing meeting--20160427I. Standing meeting Information After the early morning discussion, the panellists decided on the tasks to be carried out today, summed up the work carried out yesterday and the difficulties encountered, and analysed the unfinished work.Group "Standing meeting", there is a figure with the truth:Ii. Schedule of tasksAfter yesterday afternoon's personal project and the evening of the integration of the discussion, our first phase of the product has a considerable pr

project/team, covering the whole life cycle of product development, designing operation process and usage habit from the perspective of developer, integrating Gantt Chart, SVN, Kanban, logbook, statistic report and other practical development management tools, discarding tedious process and standard-oriented thought, The page is concise and the flow is clear. Mantis 1. Built-in report generation features (includ

Conference Pictures: meeting Content: Zouhaoujan: Yesterday: The operation of the database has a general understanding; Today: Create Add, modify, delete, query student information function, and exit the main interface; problems encountered: How to display the Web address as a hyperlink Liu Yang: yesterday: A detailed understanding of the database, and proceed with the implementation of code; Today: The realization of the use of the database into the program, to assist in the completion of addin

1. Standing meeting Information:Identify the team goals for today and identify the tasks for everyone on the team.2. Task Progress:Lu Guanghao: Consolidating database content and the entire programJing: Dealing with problems with the integration interface, including page layouts, code clutter, and moreEuna Lee: The icon for the design app, and the short wait screen diagram after the software is opened.Wang Shuo: rectification and repair of some functions after integration3. Task

1. Standing meeting Information:Determine the task of the day and define the team's goals in detail.2. Task Progress:Meng: Check the results screen, according to the school year and semester to inquire.Jang-hoon: My schedule interface, will query out the results, displayed in the table.Yu Lei: User feedback interface, user input box was beautified.Wang Yu: The login interface calls to each other, as well as part of the Setup interface.3. Task Kanban:4

Daily Standing meeting--20160423I. Standing meeting Information After the early morning discussion, the panellists decided on the tasks to be carried out today, summed up the work carried out yesterday and the difficulties encountered, and analysed the unfinished work.Group "Standing meeting", there is a figure with the truth:Ii. Schedule of tasksWe still continue to interface, change the interface, write pause music and timing function, although the efficiency is a little low, but we firmly bel

1. Standing meeting Information:Determine the lab tasks for the team members this day, discuss specific scenarios for solving the problems each person encounters, and the learning tasks that need to be completed today.Photo of standing meeting:2. Task Progress:This paper discusses the interface design and the concrete interface design steps, and has completed the first stage interface design.Learn about UI design and learn how UI is designed for the user interface. Continue to learn the UI inter

cycle of the service, working in a separate context, making decisions on its own governance without needing a unified command center. Teams and teams connect through loose community tribes. We can see the idea of the entire microservices as we now face the explosion of the explosive, knowledge explosion is the same: by decoupling what we do, divide and conquer to reduce unnecessary losses, so that the entire complex system and organization can quickly respond to change. Why do we use micr

%E7%82%BA%E4% bd%95%e6%9c%83%e6%af%94%e8%bc%83%e5%bf%ab/Related reading: The power of Seeing – (I) Thinking of solving problems Power of Seeing – (II) Impact map User story-driven agile development –2. Create a backlog User story-driven agile development –1. Planning Chapter Analyzing the five core practices of lean product development – Kanban approach Impact Mapping Influence Map reading and exercise experience 8 Ste

System Linux/ubuntu 14.04.5 LTS (trusty Tahr) + ROS Indigo Linux/ubuntu 16.04.1 LTS (xenial Xerus) + ROS Kinetic Web Explorer Google Chrome C + + IDE Xcode (MAC) Netbeans Qtcreator Codeblocks (Windows) Python IDE Spyder Pycharm Java IDE IntelliJ idea Eclipse Math/matrix computation Matlab Octave Editor Sublime Text 3 notepad++ (Windows) Gedit Vi/vim Emac D

completion of the second phase, the next is the most important integration phase, constantly to optimize the interface, that is, the design of UI interface, as the administrator of us, we manage the function of the data in advance, as far as possible to complete the function of the private messages, this stage is an important stage of market-oriented, if the interface can not attract customers Then we have a powerful and useless function, so we want to attract the attention of customers, we wil

1. Standing meeting Information:Identify the team goals for today and identify the tasks for everyone on the team.2. Task Progress:Lu Guanghao: Consolidated revenue, expense interface and linked database.Jing: Integrated login interface and side-slip interface.Euna Lee: With other team members to integrate some of our interface and database docking, beautify the main interface, to achieve the main interface button function.Wang Shuo: Realizing the specific integration of each part3. Task

function of the product with the minimum cost to achieve, and then quickly solicit the user's opinion. and MBP production ideas, is the strongest and most beautiful product strategy.The 6th chapter mainly tells us the agile development process. An overview of the agile development process begins with the first step: finding out what needs to be done to complete the product--prouduct Backlog. Step two: Decide what you need to solve for your current sprint. Step three: Sprint, Sprint, you need to

, and put them into the next sprint's product requirements;Here are some of the scenario diagrams used in the scrum development process:is an example of a Product Backlog.Is the daily standing meeting, the participants can stand at random posture, task Kanban to ensure that everyone see, when everyone after the speech, to go to the task version before the update their Burndown chart.The task view contains incomplete, in-progress, completed work, assum

My-hr Members: Role Assignment School Number Blog Park Team Contribution points Khuhuhimin PM Project Manager 201406114203 http://www.cnblogs.com/qiuhuimin/ + General Ming Yin User 201406114204 http://www.cnblogs.com/mingyin/ 19 Wolf Product Owner 201406114227 http://www.cnblogs.com/range/ 18 Candidly Scrum Master 201406114229 http

I. Standing meeting InformationIt has been 3 days since the last meeting and the pre-selection of the seats has been completed. But the time control module is not reasonable, but also need to modify, so today's meeting content is, the preselection module to modify.Ii. Schedule of tasksBecause of the time is tight, this time progress is not very fast, but very stable, every day has effect, slowly, I believe that will not be many days, our library assistant can be published, for the vast number of

Copy card:Click the Copy Card button to the right of the card to copy the card to the list of the target Kanban, and all the contents of the card will be copied.To view task tracks:A task track is a historical trajectory from the start of a task to the current state.To delete a card:There are two ways to delete a card:1) Click on the Delete button on the card to delete it directly.2) Click on the card, go to the card page, select Delete Card button to

1. This cycle is relatively short, or according to the previous sprint process requirements, backlog-Kanban-Burndown chart-Daily stand, etc., and reflected on the blog.2. Demo time: June 2016 21 pmThe demonstration can refer to the graduation design reply, which contains two parts:Project presentation, which summarizes the project, team, development process, etc.Run demos, implement functions, business, user feedback, and more.Hope that the group care