یادگیری یک چیز جدید هر روز
A fishbone diagram (also known as a cause and effect diagram or Ishikawa diagram) visually shows multiple causes of a problem. It helps identify stakeholder ideas about the cause of an issue and allows users to immediately categorize ideas into themes for analysis or further data collection. It can be used in conjunction with the “Five Whys” technique.
Continue reading
A use case describes how a user uses a system to accomplish a specific goal. A use case diagram consists of a system, related use cases, and actors, and relates them to each other in order to visualize: what is being described? (the system), who is using the system? (actor) and what the actor wants to achieve? (use case), so that use cases help ensure that the right system is developed by capturing the requirements from the user’s perspective.
Continue reading
The Business Process Management Initiative (BPMI) has developed a standard Business Process Modeling Notation (BPMN). The BPMN 1.0 specification was released to the public in May 2004. The specification represents more than two years of work by the BPMI Notation Working Group. In February 2006, the OMG released a BPMN specification document. Version 2.0 of BPMN was developed in 2010 and the actual version of the specification was released in December 2013.
Continue reading
The project imitation document defines the project scope, management, and overall success criteria that the team can look back on during the project. It contains basic information about the project, such as context, scope, team and collaboration. It is equally important as an internal guide and an external stakeholder
Continue reading
A communication plan is a policy-driven approach to providing information to stakeholders. The plan formally defines who should receive specific information, when that information should be provided, and what communication channels will be used to provide the information.
Continue reading
Modern and effective project management techniques require skills that allow the seamless integration of best practice tools with good leadership and team management within an organization for improving the likelihood of success of time-limited initiatives. These practices include establishing clear accountabilities, defining objectives and outcomes, establishing the scope, planning, monitoring, and reporting controls for project activities.
Continue reading
Seamlessly navigate the entire scrum process in a single, beautifully designed scrum process canvas. Perform scrum activities quickly, easily and seamlessly. Keep the whole team fully engaged. Our agile software makes agile projects simple and effective.
Continue reading
A plan-driven process means that all process activities are planned in advance and progress is measured against that plan. In an agile process, the plan is incremental and it is easier to change the plan and software to reflect changing customer needs.
Continue reading
Sprinting is running over a short distance in a limited period of time. It is used in many sports that incorporate running, typically as a way of quickly reaching a target or goal, or avoiding or catching an opponent. A sprint is a time box. Each sprint has a start and end date during which a set of selected user stories have to be completed and confirmed. The following image shows you the key elements of a sprint, which includes a set of user stories, the scrum members involved, the assignment of work, the duration and end date (top-right corner).
Continue reading
Some people are very proficient in a particular field, but rarely contribute outside of that field. These people are called “I-types” in the agile community because they are like the letter “I” in that they have depth, but not much breadth. In contrast, “T-people” have complementary expertise in one area, but less developed skills in related areas and good collaboration skills.
Continue reading