optivem / optivem.github.io Goto Github PK

• Starts with conflict
• Inciting incident is the point of the plot that begins the conflict
• This catalyzes protagonist to go into motion and take action, protagonist understands goal, works towards it, smaller problems thwart initial success, progress directed towards secondary obstacles which the protagonist overcomes
• Rising action = build of events until climax

Source: https://en.wikipedia.org/wiki/Plot_(narrative)

• Project management process
• Product management process
• Project structure

• JIRA, confluence
• Formal and informal
• documentation, contracts
• Protection, risk, miscommunication

• Standards, guidelines, best practices for high-performance IT organizations
• Codex vs opticodex (branded)
• Promoting standards don't reinvent the wheel, basis for training and helping organizations out this into practice ==> standards are the product for website
• Further development - milestones for codex releases
• Get in touch, suggest something additional

• Setup https://stackoverflow.com/questions/21446165/how-do-i-use-disqus-comments-in-github-pages-blog-markdown

• Allow both registered and anonymous

• Based on responses, clarification do request, making ticket and linking to comment - write workflow

• Currently the website is just in English, however, translations are planned for the future. For commenting, you can write in the following languages: English, Serbian, German.

• For empty pages - jumbotron - start a discussion, tell me what to write about, and also setting the first comment with brief overview of this page and inviting comments, same text as jumbotron

• Checking if comments should be on all pages, or just codex & blog? In that case, differentiated layout

• Explain collaborative approach and crowdsourcing to get ideas what people need in practice

• Core perspective - helping organizations and people, what problems do they have? Offering solutions...

• Before starting - Check URLs, Opticodex Vs codex, splitting pages or merging, changing URLs, Moderation rules

• Write posting ideas - questions, comments, sharing experiences, alternative viewpoints, requests for more information, reporting errors; personal or from others' perspectives

• Focus on benefits for the readers - what they get, knowledge and opportunity to drive their organizations

Organizational culture, team culture, agile perspectives, self-organized teams

Roles:

• Project manager
• Product manager / product owner
• Scrum master
• Business analyst
• Project Portfolio manager

Tasks:

• Roles & responsibilities
• Translation between traditional and agile
• How they communicate / interact
• Where are they in product and project methodologies

• Turning point / highest point of story, protagonist makes big decision that defines not just story outcome but also who they are as a person
• Protagonist finally clears preliminary barriers and engages with antagonist, both have a plan to win against the other, direct conflict
• Usually each one partially sucessful
• In this central struggle, protagonist makes a decision that shows moral quality and determines outcome

Source: https://en.wikipedia.org/wiki/Plot_(narrative)

• Box where reader can suggest improvement
• This is mapped to issues, new issue of type suggestion / idea / proposal / enhancement

• Including tagline
• Including images
• Focusing motivations / problems / challenges / wishlists
• Providing Opticodex as solution, and linking to it, perhaps also brief overview of its sections, and Read more button
• Additionally at end, perhaps About and Contact

• Consists of events leading to the ending
• Character's action resolve the problem
• Often at beginning here antagonist has the upper hand, protagonist never further from goal
• Outcome depends on the side on which protagonist goes

Source: https://en.wikipedia.org/wiki/Plot_(narrative)

• Protagnost and antagonist solved their problems
• Either wins the conflict, conflict officially ends
• Some stories show what happens to characters after the conflict ends or in the future

Source: https://en.wikipedia.org/wiki/Plot_(narrative)

• Deployment
• Configuration
• Servers

• Reader can report incorrectness, either something small like spelling mistake or something bigger like incorrect content or alternatives
• This is mapped to Issues type: bug

Corporate values

When this is done, link it from Vision page and from Culture page

• Situational leadership, inspirational, transformational, motivational approaches
• Leadership psychology
• Values, motivation, organizational culture, how to recognize leaders, how to grow and develop leaders, empathy, situational awareness 

Describe motivation, principles, big picture.

Not sure if to call it Foundations / Core / Crux / Principles...

• Introduce characters, esp. protagonist
• Show how characters relate to one another, esp. goals and motivations, moral character
• Protagonist learns their main goal and what is at stake

Source: https://en.wikipedia.org/wiki/Plot_(narrative)

• Agile
• Waterfall

Documentation types:

• Product Documentation: case study (what was issue), business case (or mixed), system requirements specification (SRS), synonyms / acronyms
• Project Documentation: traditional: project plan, resources, budget, scope, WBS... agile: _______ (agile handling of milestones)... Comparisons, when to use agile, when traditional, compare documentation for both of these.... i.e. not just process but documentation
• Technical Documentation: Architecture. Technical specifications for database, API etc. Integration with other systems
• Process Documentation: Company wide policies and procedures. For all teams, regardless of project.

Benefits:

• For each one, an example, and why, what are the benefits (e.g how this relates to success)

Handling getting responses to no:

• We don't have time for it
• The client does not want to look at it
• There are so many changes and we can't keep up
• I don't know what documentation to write
• I don't have time for 100 pages, too much
• No one will read it
• We don't have budget for it

Budgeting:

• Budgeting - documentation...

• Confluence
• JIRA

• Growing high performance IT organizations (people, process, product) - 3P3s - (who/we/are, how/method, what/result)
• Improvement / growth / high performance at every level (cross hierarchy - vertical and horizontal)

• Projects
• Milestones
• Labels
• Wiki

• Reader can ask a question, and this could go to Issues perhaps?
• Can be anonymous if via box or if leave name / email or directly create ticket on GitHub with type: question

• Check possibility for voting for ideas, maybe survey or prioritization
• This would ensure that content is added in value-based way