{"id":29732,"date":"2023-11-27T18:59:10","date_gmt":"2023-11-27T17:59:10","guid":{"rendered":"https:\/\/scrum.sk\/tim\/assessing-the-state-of-agile-practices\/"},"modified":"2024-01-30T10:30:13","modified_gmt":"2024-01-30T09:30:13","slug":"assessing-the-state-of-agile-practices","status":"publish","type":"ponuka","link":"https:\/\/scrum.sk\/en\/tim\/assessing-the-state-of-agile-practices\/","title":{"rendered":"Assessing the state of Agile practices"},"content":{"rendered":"\n\t
\n\t
\n

\n Certifikovan\u00fd <\/p>\n <\/div>\n \t\t

<\/div>\n\t\t\t\t\t
\n\t\t\t\"background-pattern\"\n\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t

Assessing the state of Agile practices<\/h1>\t\t\t\t\t\t

Agiln\u00fd t\u00edm<\/h2>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t

Hodnotenie prakt\u00edk<\/h2>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t

Identifikujte potenci\u00e1l pre zlep\u0161enie agiln\u00e9ho t\u00edmu. Validujte nastavenie t\u00edmu, nastavenie produktu a procesov, ich aplik\u00e1ciu va\u0161im t\u00edmom a pou\u017e\u00edvanie JIRA sk\u00fasen\u00fdmi mentormi, ktor\u00ed podporovali u\u017e stovky t\u00edmov pri zav\u00e1dzan\u00ed Agile, Scrum, Kanban, DevOps a SAFe.<\/p>\n\t\t\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\tObjedna\u0165<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tViac inform\u00e1ci\u00ed<\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\"img\"\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t<\/section>\n\n\n
\n
\n
\n
\n\n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
Pre koho<\/h5>
T\u00edmy aplikuj\u00face agiln\u00e9 praktiky a metodiky ako napr. Scrum, Kanban, SAFe, DevOps, Spotify model.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
Trvanie<\/h5>
Pribli\u017ene 6 dn\u00ed.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
Forma<\/h5>
Onsite, alebo online \u00fa\u010das\u0165 na stretnutiach. Vzdialen\u00fd pr\u00edstup k JIRA, resp. in\u00fdm elektronick\u00fdm n\u00e1strojom pou\u017e\u00edvan\u00fdm t\u00edmami.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n\n \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n\n\n
\n
\n
\n
\n
\n \"roadmap\"\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n \n\n
<\/div><\/div><\/div><\/section>\n\n\n
<\/div>\n\n\n\n

Evaluation<\/h2>\n\n\n\n

Areas <\/strong><\/h2>\n\n\n\n
<\/div>\n\n\n\n
\n
\n

Meeting<\/p>\n\n\n\n

Preparation<\/h4>\n\n\n\n

Evaluation<\/strong><\/h4>\n\n\n\n

Identification of client expectations. Setting activity goals. Analysis of the client’s business environment, customers, products and projects. The team, its abilities and dysfunctions. Review of business and development processes. Systematic limitations. Tools used.<\/p>\n<\/div>\n\n\n\n

\n

Observation<\/p>\n\n\n\n

Agile <\/h4>\n\n\n\n

Ceremonies<\/strong><\/h4>\n\n\n\n

\u00da\u010das\u0165 ScrumDesk mentora ako pozorovate\u013ea na z\u00e1kladn\u00fdch t\u00edmov\u00fdch cerem\u00f3ni\u00e1ch ako napr. pl\u00e1novanie denn\u00e9 stand-upy, sprint review a retrospekt\u00edvy.<\/p>\n<\/div>\n\n\n\n

\n

Analysis<\/p>\n\n\n\n

Team<\/h4>\n\n\n\n

Tables and metrics<\/strong><\/h4>\n\n\n\n

Analysis of artifacts recorded in an electronic tool (JIRA, Azure DevOps, etc.). <\/p>\n\n\n\n

Identification of the potential for improving the requirements record, product backlog management, progress record discipline, metrics analysis. <\/p>\n\n\n\n

Identification of typical errors and proposals for their elimination in the most practical way possible.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Analysis<\/p>\n\n\n\n

Agile<\/h4>\n\n\n\n

Team<\/strong><\/h4>\n\n\n\n

Analysis of typical team dysfunctions. Online questionnaire with subsequent evaluation of the level of team dysfunctions and recommendations for overcoming them.<\/p>\n<\/div>\n\n\n\n

\n

Meeting<\/p>\n\n\n\n

Personal <\/h4>\n\n\n\n

Interviews<\/strong><\/h4>\n\n\n\n

Personal interviews with key people representing product and project management roles, team leaders and selected team members.<\/p>\n<\/div>\n\n\n\n

\n

Result<\/p>\n\n\n\n

Elaboration<\/h4>\n\n\n\n

Proposals for changes<\/strong><\/h4>\n\n\n\n

Vypracovanie hodnotenia pozit\u00edv aktu\u00e1lneho stavu implement\u00e1cie agiln\u00fdch prakt\u00edk. Zhodnotenie potenci\u00e1lu pre ich zlep\u0161enie a \u010fal\u0161ie odpor\u00fa\u010dania, ako ich zlep\u0161i\u0165. Osobn\u00e1 komunik\u00e1cia v\u00fdsledkov.<\/p>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n
\n
\n
\n

We thought we could operate agile quite effectively. Scrum has been implemented here for a long time and we felt that it was also of good quality. However, the depth of knowledge after the ScrumDesk audit allowed us to understand the potential for cheap and fast changes breaking the blocks and myths of Agile that we had created ourselves.<\/p>\n<\/blockquote>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n
\n
\n
\n
\"ScrumDesk<\/figure>\n\n\n\n
\"scrumdesk<\/figure>\n\n\n\n
\"scrumdesk<\/figure>\n\n\n\n
\"scrumdesk<\/figure>\n\n\n\n
\"scrumdesk<\/figure>\n<\/figure>\n\n\n\n
<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Is it suitable for you?<\/h4>\n\n\n\n

You have a team applying agile principles, practices and procedures.<\/p>\n\n\n\n

You want to find out:<\/p>\n\n\n\n