یادگیری یک چیز جدید هر روز
Most Agile and Scrum training courses refer to a 7 +/- 2 rule, that is, agile or Scrum teams should be 5 to 9 members. Scrum enthusiasts may recall that the Scrum guide says Scrum teams should not be less than 3 or more than 9. Where does this thumb rule come from? and Why?
Continue reading
Today I would like to use Visual Paradigm to demonstrate how to perform task planning for team members who will take up the RACI roles and these tasks in the Enhanced PERT Chart can automatically be assigned to the automated task manager called “Tasifier” for project management. A traditional PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. The enhanced PERT Chart tool adds four additional features for integrating with different Visual Paradigm building blocks. You can do all these within an enhanced PERT Chart modeler.
Continue reading
According to Deloitte research, “digitally advanced small businesses” earned more revenue per employee, were more likely to create jobs. The truth is, those who don’t embrace technology may be left behind! And yet, four of five U.S. small businesses aren’t taking full advantage of digital tools available to them. Today I would like to introduce an easy form builder for generating database applications without any IT technical background or coding, such as survey form, student questionnaire, order form, registration form and etc.
Continue reading
LeSS was created by Bas Vodde and Craig Larman from practical experience in scaling up Scrum, founded as the LeSS Company in 2014. The “More with LeSS” principle is at the heart of LeSS (Large Scale Scrum). Complex product development doesn’t require complex solutions. It requires a deep understanding of the essence of the problems, which can then be solved with simpler solutions.
Continue reading
This Article will show you how to effectively apply UML modeling in both agile and just-in-time manner with the powerful Model ETL feature. A UML model or diagram is a specific view into what you are trying to understand in a specific context.
Continue reading
Business Process Diagram is a very good tool to model the workflow for your company or department because it gives a clear picture about who is responsible for a particular task as well as the flow of the process. However, the Business Process Diagram does not tell us how a particular task should be performed.
Continue reading
A decision table is an excellent tool to use in both testing and requirements management. Essentially it is a structured exercise to formulate requirements when dealing with complex business rules. In a decision table, business logic is well divided into conditions, actions (decisions) and rules for representing the various components that form the business logic.
Continue reading
We always come across these terms in software development. Sometimes people a piece of software feature — requirement/ use case, backlog items …. What is the convention of the software people for using that or which?
Continue reading
In software development , the usual “estimation” includes a quantitative evaluation of the work required to perform a given development task; this is usually expressed in terms of duration (hour / day) or estimated unit (story point). The purpose is to consolidate a number of such individual estimates in order to obtain an indication of the overall duration, work or cost of the software project.
Continue reading
A UML use case diagram is the primary form of system/software requirements for a new software program under developed. Use cases specify the expected behavior (what) of a system, and not the exact method of making it happen (how). A complete set of use cases specifies all the different ways to use the system and therefore defines all behavior required of the system bounding the scope of the system.
Continue reading