Belajar satu hal baru setiap hari
Brainstorming is a group creativity technique by which efforts are made to find a conclusion for a specific problem by gathering a list of ideas spontaneously new ideas and possibilities. It’s a classic method widely used in business activities such as problem-solving, failure analysis, new product ideas, sales increasing, product improvements, etc.
Continue reading
CMMN is a graphical notation used for capturing work methods that are based on the handling of cases requiring various activities that may be performed in an unpredictable order in response to evolving situations. Using an event-centered approach and the concept of a case file, CMMN expands the boundaries of what can be modeled with BPMN, including less structured work efforts and those driven by knowledge workers. Using a combination of BPMN and CMMN allows users to cover a much broader spectrum of work methods.
Continue reading
Gap analysis involves the comparison of actual performance with potential performance. For example, a company does not make the best use of current resources, it may perform below an idealized potential. In other words, gap analysis is the process people use to examine their current state (or as-is process) with their desired state (to-be process) of a company. It typically is used to determine if the company is meeting expectations and effectively using resources that measure time, money and labor. The management team can then create an action plan to move the organization forward and close the performance gap.
Continue reading
Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
Continue reading
Cross functional flow charts show who did what and when in swimlane or grid charts. These charts are organized into multiple parts to provide additional dimensions by assigning each process step to a category. In other words, you can use a cross functional flowchart to describe the relationship between the steps in the process and the department or functional area responsible for those steps.
Continue reading
A Use Case describes a task that is performed by an actor yielding a result of business value for a business. A use case may be visualized as a use case diagram or/and in structured textual specification format:
Continue reading
Agile is a philosophy of providing solutions that encompass and facilitate evolutionary change throughout the life cycle of a product/project. Many agile teams and organizations have been using Agile to deliver software faster, improve quality, and ultimately improve customer satisfaction.
Continue reading
User stories are part of the agile approach and help shift the focus from writing requirements to discussing them. All agile user stories include one or two written sentences and, more importantly, a series of conversations about the desired functionality.
Continue reading
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage. The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them as shown in the Figure below:
Continue reading
Whether a team is developing a product or a project, we need to answer the question “When will we be able to finish it?” , or how far we will be able to go at a certain point in time, so as with traditional development models, we need to estimate the workload before we start the project. Agile estimation is the process of estimating the effort required to complete a priority task in the product backlog. This effort is usually measured in terms of the time required to complete that task, which in turn leads to accurate sprint planning.
Continue reading
English
简体中文
繁體中文
Deutsch
Español
Français
العربية
Italiano
Português
日本語
Nederlands
Bahasa Indonesia
Русский