<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leadership on Piotr Kosmowski</title>
    <link>/docs/notes/leadership/</link>
    <description>Recent content in Leadership on Piotr Kosmowski</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>pl-pl</language><atom:link href="/docs/notes/leadership/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enterprise Project Structure</title>
      <link>/docs/notes/leadership/project-doc-structure/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/leadership/project-doc-structure/</guid>
      <description> Home Page # Overview of the project Links to key sections Team members and roles Important announcements or updates Project Documentation # Requirements # Business Requirements Functional Requirements Non-Functional Requirements Architecture # System Architecture Diagrams Technology Stack Integration Points Design # UI/UX Design Guidelines Wireframes and Mockups Design Patterns Development # Coding Standards # Language-specific guidelines Best practices Version Control # Git branching strategy Repository structure Build and Deployment # CI/CD Pipeline Documentation Deployment Procedures Environment Setup Testing # Test Plans # Test Strategy Test Cases Quality Assurance # QA Processes Bug Tracking User Acceptance Testing (UAT) # UAT Criteria Feedback Collection Operations # Monitoring and Logging # Monitoring Tools Log Management Incident Management # Incident Response Plan Post-Mortem Documentation Maintenance # Scheduled Maintenance Procedures Backup and Recovery Plans Team Collaboration # Meeting Notes # Regular Stand-ups Sprint Planning Retrospectives Decision Logs # Key Decisions Made Rationale Behind Decisions Knowledge Sharing # Internal Workshops Training Materials Resources # Templates # Document Templates Meeting Agenda Templates Tools and Software # List of Tools Used Access Information External Resources # Links to Relevant Articles Industry Standards and Guidelines FAQs and Troubleshooting # Common Issues and Solutions Frequently Asked Questions Troubleshooting Guides Change Management # Change Request Process Change Log Impact Analysis </description>
    </item>
    
    <item>
      <title>Leader Toolbox</title>
      <link>/docs/notes/leadership/leader-toolbox/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/leadership/leader-toolbox/</guid>
      <description>Overview # The Leader Toolbox is a collection of tools, techniques, and resources designed to help leaders effectively manage their teams, foster collaboration, and drive performance. This toolbox includes methods for feedback, team agreements, and communication strategies.
The Leader Toolbox is designed to equip leaders with the necessary tools and techniques to foster a positive and productive team environment. By utilizing these resources, leaders can enhance communication, drive performance, and build strong, collaborative teams.</description>
    </item>
    
    <item>
      <title>Scrum template</title>
      <link>/docs/notes/leadership/scrum-template/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/notes/leadership/scrum-template/</guid>
      <description>Scrum # Sprint length # 2 weeks, planning at the start, review at the end, starting Tuesday or Wednesday (1 to choose) (a lot of meetings on Monday).
Roles # Product Owner – the only person responsible for items in product backlog and it’s prioritisation. One person. Scrum Master – facilitator for the team, helps in impediments removal (Bartlomiej Labno/Piotr Kosmowski + rotational team support) Developer – member of the team Scrum team consists of PO, SM and Developers.</description>
    </item>
    
  </channel>
</rss>
