Archive | Scrum process RSS feed for this section

Writing “Confessions of a dangerous mind”

11 Oct

I was thinking about “Confessions of a dangerous mind” with Sam Rockwell when writing the title. Truth is the post has nothing to do with the movie, so everyone interested in the movie – feel free to skip the article or search for better places.

Here is a copy of a poster for the movie fans not to feel bad. This was just to get your attention

sam rock

This year I was involved as a co-organizer of a Product Stream at IT Arena Lviv conference 2015 (itarena.lviv.ua). Prior to this I have organized just one event – Eleks Battle of the bands in 2013 – so I can’t say I have a wealth of experience in the area. My main responsibilities this year were to guarantee quality content i.e. find speakers and ensure they present at the event. I have found a few interesting folks (according to feedback I’ve heard) but now I realize how far the initial plan was from the actual execution. This post is a braindump of things I wanted to share after the conference. Some of ideas require a lot more elaboration and deserve separate posts. If you have enough patience to go through this – then maybe you can spend even more time and share your ideas and experience in event management via comments to the post

  • Design of the event
    • Waterfall is still alive. Almost any event is a great example of waterfall. This is particularly valid for conferences. This means that all phases preceding to the actual execution take 99% of time and therefore need to be thought through for the execution to go well
    • It is essential to define goals of the event. I knew goals of Eleks as the company I represented as a co-organizer of product stream but I did not know goals of the rest of key organizers. This made me narrow-minded in understanding the attendees of other streams
  • People buy tickets to the conference and not a certain stream
    • Attendees don’t distinguish Product stream or Business stream or whatever stream as different parts of the conference. For them this is a single experience for which they have paid money and they expect the same level of quality and experience at any speech of any stream they attend. They don’t know the conference streams may be organized by different people or teams or they don’t care about that. They care about 3 days they spend at the conference
    • This means there has to be consistent work among stream leaders to help one another with speakers, content, promotion and any questions that arise as the conference is a shared responsibility. Failure of one stream becomes a failure of the entire conference
  • Guidelines for presentations – how to define a high-quality presentation
    • What should be inside content-wise
      • Takeaways
      • Learning outcomes
      • Text + image combo or text limits
    • Font size
  • Presentation censorship
    • Should not be 1 person making a decision about speakers
    • Should be a group of 2 or 3 that review on a regular basis to ensure unbiased decision
    • Keep track of all speakers who have already participated
    • Introduce a mechanism for rating speakers to decide whom to invite
      • Past experience
      • Topic
      • Presentation skills
      • Past ratings
      • Personal knowledge of the speaker
      • Travel cost
      • Cost of stay
    • Work with speakers – iterative approach
      • Central idea
      • Main takeaways/conclusions
      • Slide titles
      • Actual meat
      • Visuals
      • Presentation
      • Define timeframe for each stage – should be completed well enough before conference
      • Train speakers to present or check their presentation skills / if a speaker doesn’t agree – let them go and don’t let them participate
    • Substitute speakers
      • High risk that should be considered
      • May be needed to find 2-4 substitute speakers
      • Should be given some form of presenting at the conference not to feel second best
    • Workshops
      • People need to be motivated to come to workshops
      • Workshops should be paid separately
      • Integrated environment – buy conference ticket, workshop ticket or combo
      • Prepare real cases for audience
      • Collect audience expectations
      • Promote workshops through opinion-makers
    • Work with top level management
      • People at the top are often there for a reason and could be strong proponents of ideas so they should at least be made aware of opportunities. From there they can figure out who to involve
      • Senior people should be kept in the loop from the very beginning as that helps to generate even more ideas
    • Food catering
      • Lines like they are don’t always work. Lines helped Tom Gilb to start speaking to Alex Skrypnyk but that could be a rare exception
      • Need to think of ways to get speakers holding the floor right after lunch to eat quickly
    • Inviting speakers
      • A formal letter is not really important. Time is money. It is more important to check speaker’s availability on time than to spend a couple weeks preparing an official letter to find out it is already too late to invite the speaker
      • Timeliness of the invitation is key (6-8 months in advance)
      • Graphics is important – visual part of the invitation should be there
    • Keynote speakers
      • Keynote should be someone known by everyone regardless of age. That person should be the candy everyone is looking for
      • Keynotes deserve to be paid
      • Keynotes should make the people want to attend everything at the conference
      • Keynotes should be fun
    • Conference language
      • There should be one language of the conference. Speakers should be checked against that language. Questionable statement
    • Conference timing
      • There should be breaks between presentations to give people enough time (5-10 minutes)
      • Don’t put a keynote for 9am on days after registration or promote the keynote
      • The number of presentations in one day should probably not be higher than 8 (considering 40 minute long or so)
    • App improvements
      • Engage attendees more into conference by introducing more features than attendify app (rebranded for it arena) has
      • Local Bas and UX experts can be involved into design and development of those extra features i.e. thing feature through and mock it up
        • Reminder to rate speaker at the end of the speech
        • Other ideas tbd
      • People should start using the app a lot earlier than the conference starts
    • Screens and places
      • If there are tv screens available they all can be used to show conference speakers or presentations in real time not like this time where a bunch of screens was showing a static image for 3 days of the conference
      • Adjustable screens or better / larger screens
      • Multiple working screens in rooms with columns
    • Speaker companions
      • There should be someone responsible for either a foreign speaker or a keynote speaker and helping them get in touch with key people from different companies
      • There should be a person who is able to lead networking and serve as the connector between speakers and different executives/key people present at the conference
    • Talk to other related conference leaders and get them onboard to promote the event
      • Not direct competitors i.e. not happening around the same time
      • In this case, invite leaders of conferences like UXPoland, Agilia to get advice from them before and after the event
    • Conference experts
      • In case the organizers (or one of them) is not a professional organizer, there should be a 3rd party consultant involved to help with pressing issues)
      • This will help to ensure many of items outlined above are at least known and considered
      • This is what of one of the speakers mentioned to me in a dialog. “Let’s say you have google, internet, scalpel and you need to do a surgery on a heart of a friend. What will you do? Call a professional or rely on youtube videos?” and this makes sense as there are professionals who have already done quite a few things to get a knack on what needs to be done to make a conference successful
Advertisements

Business Analysis Work Planning Mistakes

15 Mar

In this article the author investigates most common mistakes of a business analyst during product/project analysis phase

Main mistakes include:

  1. Lack of domain glossary needed for the project (half checkmark)
  2. Poor expectations management from analysis phase – not asking customer regarding what they expect to get as a result of analysis
  3. Not agree on templates/format in which analysis results are delivered (Checkmark)
  4. Not try to elicit and outline customer’s risks
  5. Don’t try to reuse past experience  – very challenging to do in reality
  6. Try to follow the process without understanding what to do
  7. Lack of clarity regarding what to do next (half checkmark). A lot of information was requested but it was not properly analyzed in fact

Conducting my first BA+UX workshop

27 Oct

The idea of the event was to investigate an internal process of business travel management and to identify existing pains and try to address them using

  • combination of business analysis and UX techniques
  • a lot of clever heads
  • prototype a possible solution

This is more of a followup to make sure the important items are not forgotten

What I did good:

  • game for group dynamics and to set the mood (marshmallow challenge with spaghetti)
  • eliciting expectations from everyone
  • getting everyone involved and active (I am particularly happy that some of the participants who I’ve not seen very active in the past felt involved and contributed)
  • got peopple interested – in the end a part of the group (3 people out of the original 6) were interested in further work and stayed after the expected closing time (6pm)
  • managed expectations more or less, 50-75% expectations were reached for a part of group (2 out of 3, 3 out of 4)
  • logistics (supplies, food, materials) – as there was a dedicated team member

What I did poorly:

  • i did not organize the knowledge exchange prior to the meeting
  • interviews were not monitored to ensure the questions were valid and to the point
  • facilitation during the training session was not quite there and there were a lot of distractions
  • managing scope of the event. the overall plan was too ambitious
  • defining the scope of responsibilities
    • there was a huge gap here as the other person who co-organized the event felt the overall idea has changed and everything should have been done differently
    • in practice very few of the original objectives have been reached need specifics here

general observations

  • this was not a workshop but more of an initiative/project ->format should have been different with the current team
    • one team doing everything end-to-end
    • many teams doing different projects
    • not one team working out using parts of the process
  • still, there are people who are interested in getting this done
  • i should have prepared better in terms of BA work
    • NOT all stakeholders have been identified
    • introduction on the matter should have been better
    • needed to focus on a smaller piece that could have been swallowed in one take
    • need to learn BPMN and EPC better to be able to quickly use those notation models
  • i need to build my team to do things like this better

Quick action list after Lviv IT Arena 2014

4 Oct

After the conference is over and I still remember the books/materials I should be reading soon, I’d better list them here

In terms of prioritizing the list, I think it would be as follows:

  • UML in 24h (Joseph Schmuller)
  • The mythical man month
  • The writer’s journey

then the rest

Storyboarding

7 Apr

Plans for 2013

16 Mar

Big plans for 2013:

  • become eligible for CCBA examination with 3750 hours of real project experience and take the actual examination
  • complete three technical coursera courses (system design and need to define two more). I also need to make sure I complete Introduction to Databases this March and pass
  • take a soft skills course – communication related
  • Not really BA related but very important
  • get a driver’s license
  • put together the Eleks band thing this summer

 

Discovering people

1 Feb

As I’ve just found out, one of the chief developers in the project I work on, is quite into philosophy and even writes philosophy comics. Need to bookmark this link for future reference. This finding only makes me more certain that to be a comic, the person needs to have a highly-developed left brain hemisphere. Best jokes have impeccable logic behind them even though I love absurd jokes more. But the reason I do so is because absurd jokes appear to have a broken logic behind them and I just love things that are crooked and broken